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

Update tagging strategy #20753

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Update tagging strategy #20753

wants to merge 4 commits into from

Conversation

ef4
Copy link
Contributor

@ef4 ef4 commented Sep 20, 2024

This is preparation to make it possible to have more than one published package living in this monorepo.

It changes the tagging strategy so that releases of ember-source should be tagged like v6.0.0-ember-source instead of v6.0.0.

This is preparation to make it possible to have more than one published package living in this monorepo.

It changes the tagging strategy so that releases of ember-source should be tagged like `v6.0.0-ember-source` instead of `v6.0.0`.
@@ -126,7 +126,7 @@ jobs:
run: pnpm vite build --mode=development

- name: Set BrowserStack Local Identifier
if: startsWith(github.ref, 'refs/tags/v')
if: startsWith(github.ref, 'refs/tags/v') && endsWith(github.ref, '-ember-source')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently you still cannot comment on unchanged lines on github:

Do we want to run this workflow at all for changes and or tags of @glimmer/component?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. The CI workflow is good test coverage for everything together, including @glimmer/component.

With #20751 we'll actually get better integration test coverage of @glimmer/component than we've ever had.

@kategengler
Copy link
Member

I PR'd with a more comprehensive update to RELEASE.md #20754

The only other concern I have is that PRs for @glimmer/component will show up in the changelog via script for ember.js and need to be edited out, but I don't expect it'll be high-volume, so that should be fine for now.

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.

2 participants