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.

Sign up for GitHub

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

Jump to bottom

Release v6.0.2 failed to publish #26382

Closed
2 tasks done
tunetheweb opened this issue Apr 2, 2025 · 1 comment · Fixed by #26395
Closed
2 tasks done

Release v6.0.2 failed to publish #26382

tunetheweb opened this issue Apr 2, 2025 · 1 comment · Fixed by #26395
Assignees
@caugner
Labels
bug Confirmed bugs in the repository (i.e. linter bugs), NOT browser implementation bugs. p0 Highest priority – Must be addressed in the next release.

Comments

@tunetheweb
Copy link
Contributor

What type of issue is this?

Infrastructure issue

What is the issue?

Looks like the GitHub action failed: https://github.com/mdn/browser-compat-data/actions/runs/14200810005

Meaning the version shown at https://www.npmjs.com/package/@mdn/browser-compat-data is still 6.0.1

What behavior were you expecting?

When a new release is released, it will be available to install via NPM

What version(s) of BCD is the issue present in?

  • The current BCD release
  • The current version of the main branch

Do you have anything more you want to share?

No response
@tunetheweb tunetheweb added the needs triage This issue needs to be confirmed label Apr 2, 2025
@caugner caugner added bug Confirmed bugs in the repository (i.e. linter bugs), NOT browser implementation bugs. p0 Highest priority – Must be addressed in the next release. and removed needs triage This issue needs to be confirmed labels Apr 2, 2025
@caugner caugner self-assigned this Apr 2, 2025
@caugner
Copy link
Contributor

caugner commented Apr 2, 2025 •
edited
Loading

Good catch, thank you! I reran the failed workflow now, and the package is now released.

However, let me keep this issue open to track work ensuring that this won't get unnoticed in the future. I'm thinking of adding steps to the publish workflow that adds a comment on the PR once the npm package is released, or failed to release, and ping the right folks in the latter case.

@caugner caugner mentioned this issue Apr 3, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@caugner caugner

Labels
bug Confirmed bugs in the repository (i.e. linter bugs), NOT browser implementation bugs. p0 Highest priority – Must be addressed in the next release.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ci(release): comment in release PR after publish mdn/browser-compat-data
2 participants
@caugner @tunetheweb