infra: CI manages release process

[thompson-tomo]

This introduces github workflow for managing releases. This workflow is triggered when a tag is added to a commit and performs the following:

• Set npm package version based on tag value
• Create npm package
• Uploads npm package to npm
• Create github release with npm package attached and auto generated release notes

Required steps by maintainers:

• Setup trusted publishers https://docs.npmjs.com/trusted-publishers/
• Go to github tags and starting from 0.6.0 (or earlier) create a release for each tag by clicking the create release option, followed by the create release notes option to generate release notes.

[thompson-tomo]

This has implemented the review feedback in thlorenz/doctoc#289

[thompson-tomo]

@AndrewSouthpaw / @thlorenz how can we progress this release process automation pr as this library is now ready for a release?

[AndrewSouthpaw]

Unfortunately, I don't have admin access to anchor-markdown-header in npm, only to doctoc.

@thlorenz could you add me as a collaborator so I can set this up?

[thompson-tomo]

Thanks @AndrewSouthpaw note that the CI pipeline has been defined such that even if the npm upload failed the creation of the github release would still complete. This github release would contain the files which could be uploaded to npm.

[thompson-tomo]

@thlorenz could we get some assistance/input from you so that we can do a release and then prepare to release doctoc.

[thlorenz]

Hey sorry, life was keeping me busy over the last weeks.
@AndrewSouthpaw I invited you as maintainer to the npm package.

[thompson-tomo]

No worries, thanks for doing that.

[thompson-tomo]

@AndrewSouthpaw this should hopefully be done now. 🙂

[thompson-tomo]

@AndrewSouthpaw could you please go through the process of completing a release of this library so that we can update doctoc?

[AndrewSouthpaw]

Looks like the CI failed, can you investigate? https://github.com/thlorenz/anchor-markdown-header/actions/runs/21639237686/job/62373684014

…

-- Sent from a tiny screen; please excuse brevity or errors, or both.

On Tue, Feb 3, 2026 at 07:10 James Thompson ***@***.***> wrote: *thompson-tomo* left a comment (thlorenz/anchor-markdown-header#58) <#58 (comment)> @AndrewSouthpaw <https://github.com/AndrewSouthpaw> could you please go through the process of completing a release of this library so that we can update doctoc? — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHSOTHBW7UY5IK3IOYMUXD4KCF43AVCNFSM6AAAAACQA245ROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNBQHEZTQMBUGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[thompson-tomo]

@AndrewSouthpaw sure, have you setup the trust publishing process as at a first look issue appears to be an authorisation issue?

[thompson-tomo]

@AndrewSouthpaw it appears that I might have found the source of the problem and why the gh issue wasn't created. The Workflow was using an old version of node. See #59 for details of the fix. I would suggest triggering a preview release of 0.8.1-preview1 to test after merge and do i manual upload of 0.8.0 to npmjs.

[AndrewSouthpaw]

Thanks! I confirmed the trust publishing process is set up. I'll give it another go after merging.

[AndrewSouthpaw]

Confirmed CI works now! Versions 0.8.0 and 0.8.1 are published. 🎉

[thompson-tomo]

Perfect, I will bring the changes across to doctoc via thlorenz/doctoc#311