ci: publish git tags to Github (resolves #444)

[pdecat]

Important

Adds functionality to create and push git tags in the marketplace-publish.yml workflow when publishing a VS Code extension.

• GitHub Actions Workflow:
  • Adds permissions: contents: write to publish-extension job in marketplace-publish.yml for pushing tags.
  • Adds step to create and push git tags using the current package version from package.json.
  • Tags are created as v<version> and pushed to the origin.

^{This description was created by for 8caba0fe1ad7c4e53f30da4d8e1a7a8c04b82fda. It will automatically update as commits are pushed.}

[changeset-bot]

🦋 Changeset detected

Latest commit: f99fc59

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
roo-cline	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pdecat]

Maybe move this just before publishing the extension?

[mrubens]

What do you think is best?

[pdecat]

I'd say tagging before publishing is more common.

[mrubens]

Works for me! Want to update it and then I can merge?

[pdecat]

I've moved tagging before publishing, but still after packaging to avoid tagging releases which fail to package.

[pdecat]

Also, there's #1386 suggesting to tag all previous releases using a nice script.

[mrubens]

Nice, this makes sense to me!

Separately, should we create a Github release when we publish the extension?

[pdecat]

Publishing Github releases is a great addition for seeing the changes introduced by a release directly.
I can add this to this PR if desired.

[mrubens]

@pdecat I really appreciate your help! How about I merge this one and then use another PR for creating releases?

[pdecat]

Sure 🚀

[mrubens]

Great! I'll run that command to backfill git tags now as well.

[pdecat]

There may be something to adjust in the tagging step as tags are linked to invalid-email-address
Check your git settings! user:

See https://github.com/RooVetGit/Roo-Code/releases/tag/v3.8.5

Maybe just setting GIT_AUTHOR_EMAIL in the Github Actions settings would suffice.

[mrubens]

There may be something to adjust in the tagging step as tags are linked to invalid-email-address Check your git settings! user:

See https://github.com/RooVetGit/Roo-Code/releases/tag/v3.8.5

Maybe just setting GIT_AUTHOR_EMAIL in the Github Actions settings would suffice.

What do you think of this? #1619