Skip to content

Conversation

@ddbeck
Copy link
Collaborator

@ddbeck ddbeck commented Dec 17, 2024

This produces a bunch of needless notifications for release watchers on GitHub. I think there's a way to work around this, but it needs some testing first.

This partially reverts commit 766b40e and #2428.

This produces a bunch of needless notifications for release watchers on
GitHub. I think there's a way to work around this, but it needs some
testing first.

This partially reverts commit 766b40e.
@github-actions github-actions bot added the tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings label Dec 17, 2024
@szepeviktor
Copy link
Contributor

Were you thinking about a daily pre-release?

@ddbeck
Copy link
Collaborator Author

ddbeck commented Dec 17, 2024

What I want is a continuously-updated release, so that it's easy to get at artifacts for the head of main. That is, I want to be able to curl https://github.com/web-platform-dx/web-features/releases/download/next/data.extended.json to always have the latest release data.

The existing workflow does that. However, the date never changes (previously, it appeared as if the next release was stuck in September or so, even though it changed several times a day). Deleting and re-creating the release fixes the date, but (misleadingly) makes it appear that there's a "new" release on every commit.

A little more detail here: #2068

@szepeviktor
Copy link
Contributor

szepeviktor commented Dec 17, 2024

so that it's easy to get at artifacts

I see!
You could generate GitHub Artifacts with a workflow for main.
... and use GH CLI
https://cli.github.com/manual/gh_run_download

@ddbeck
Copy link
Collaborator Author

ddbeck commented Dec 17, 2024

I'm superseding this PR with #2454, which ought to have the desired effect.

@ddbeck ddbeck closed this Dec 17, 2024
@ddbeck ddbeck deleted the prevent-prerelease-notifications branch February 28, 2025 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants