Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: don't sync semver tags for releases #275

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

EvanHahn
Copy link
Contributor

This is the equivalent to this change. To quote that commit:

The optic release option sync-semver-tags creates additional tags (v{MAJOR}, v{MAJOR}.{MINOR}) which are updated on each release. This currently does not work because this tag push happens with the permissions of the default github actions token, which does not have rule bypass permissions. It's a "soft fail" (the release still gets made), and the full version tag comes from the release creation, which is done by the optic release app, which is included in our ruleset bypass list.

We don't need these tags, and they are not working, so this [commit] turns this option off.

I plan to YOLO-merge this if CI passes.

This is the equivalent to [this change][0]. To quote that commit:

> The optic release option `sync-semver-tags` creates additional tags
> (`v{MAJOR}`, `v{MAJOR}.{MINOR}`) which are updated on each release.
> This currently does not work because this tag push happens with the
> permissions of the default github actions token, which does not have
> rule bypass permissions. It's a "soft fail" (the release still gets
> made), and the full version tag comes from the release creation, which
> is done by the optic release app, which is included in our ruleset
> bypass list.
>
> We don't need these tags, and they are not working, so this [commit]
> turns this option off.

[0]: digidem/comapeo-core@d3dc9d8
@EvanHahn EvanHahn merged commit 10261e7 into main Oct 24, 2024
6 checks passed
@EvanHahn EvanHahn deleted the dont-sync-semver-tags-on-release branch October 24, 2024 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant