Skip to content

Chore: Make new release of MarkBind action upon new MarkBind Release #2839

@gerteck

Description

@gerteck

Please confirm that you have searched existing issues in the repo

Yes, I have searched the existing issues

Any related issues?

No response

What is the area that this feature belongs to?

No response

Is your feature request related to a problem? Please describe.

MarkBind/markbind-action#18

Next release of MarkBind will be major version change due to migration to node v22

markbind-action should also make a new release alongside the MarkBind release to use Node v22

Just a reminder of task to be done as an issue.

Describe the solution you'd like

Chore to be done, if done, please close issue

If MarkBind release is done but actions not released in tandem, please ping releaser or maintainer or active developers.

Describe alternatives you've considered

Reason why release not made directly after merge in case existing workflows using latest cause the action to use node v22 while the most updated MarkBind version is tested to run on node v18

Additional context

Thanks @Harjun751 for upgrading node version

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions