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

@next GitHub release date does not advance #2068

Open
ddbeck opened this issue Oct 23, 2024 · 1 comment
Open

@next GitHub release date does not advance #2068

ddbeck opened this issue Oct 23, 2024 · 1 comment
Labels
bug Something isn't working tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings

Comments

@ddbeck
Copy link
Collaborator

ddbeck commented Oct 23, 2024

The https://github.com/web-platform-dx/web-features/releases/tag/next release is continuously updated with the latest (test-passing) commit. However, because it updates an existing tag instead of creating a new one, the release date never advances on GitHub, so it sorts oddly, to the fixed time we created the workflow, well before v2.0.0.

We ought to use some steps as described in softprops/action-gh-release#171 (comment) to automatically advance the tag date on each publish for the @next release.

@ddbeck ddbeck added bug Something isn't working tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings labels Oct 23, 2024
@ddbeck
Copy link
Collaborator Author

ddbeck commented Nov 1, 2024

While I'm at it, I think it'd be a good idea to stop using softprops/action-gh-release itself. The latest update #2131 had me dig into what was being released and why (the release notes were vague). That led me to find that the maintainership of the action has been handed over to someone else, but there's no documentation about it. Seems… iffy.

I think we can do the same with the gh CLI, something like:

run: >
  gh release create
  --verify-tag
  --title 'web-features@next'
  --notes 'This is a continuously-updated prerelease generated from `main` (currently at ${{ steps.timestamp_and_hash.outputs.SHORT_HASH }}).'
  --prerelease
  --latest=false
  next
  <artifact paths go here>

(Of course, we'll have to delete and recreate the next tag in the step preceding this one.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings
Projects
None yet
Development

No branches or pull requests

1 participant