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

Repo: 8.27.0 release was not published to npm #10972

Closed
controversial opened this issue Mar 19, 2025 · 4 comments
Closed

Repo: 8.27.0 release was not published to npm #10972

controversial opened this issue Mar 19, 2025 · 4 comments
Assignees
@JamesHenry
Labels
repo maintenance things to do with maintenance of the repo, and not with code/docs team assigned A member of the typescript-eslint team should work on this.

Comments

@controversial
Copy link
Contributor

Suggestion

The v8.27.0 release that was published to the changelog and tagged from 3efd99e is not published to npm, where the latest release is still 8.26.1; is this intentional or a mistake?

Additional Info

No response
@controversial controversial added repo maintenance things to do with maintenance of the repo, and not with code/docs triage Waiting for team members to take a look labels Mar 19, 2025
@kirkwaiblinger
Copy link
Member

Yeah, this came up in the discord as well: https://discord.com/channels/1026804805894672454/1084238921677946992/1351881633074118666

I noticed something was weird with f07bdcf, but not sure whether that's a cause or effect 🤔

@kirkwaiblinger
Copy link
Member

But, yeah, definitely not intentional!

@kirkwaiblinger kirkwaiblinger changed the title Repo: 5.7.0 release was not published to npm Repo: 8.27.0 release was not published to npm Mar 19, 2025
@kirkwaiblinger kirkwaiblinger pinned this issue Mar 19, 2025
@kirkwaiblinger kirkwaiblinger added accepting prs Go ahead, send a pull request that resolves this issue and removed triage Waiting for team members to take a look labels Mar 19, 2025
@bradzacher
Copy link
Member

This is an issue caused by our token rotation in response to the security incident. We'll get it published soon.

@bradzacher bradzacher added team assigned A member of the typescript-eslint team should work on this. and removed accepting prs Go ahead, send a pull request that resolves this issue labels Mar 19, 2025
@bradzacher
Copy link
Member

Release is now up on npm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JamesHenry JamesHenry

Labels
repo maintenance things to do with maintenance of the repo, and not with code/docs team assigned A member of the typescript-eslint team should work on this.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@JamesHenry @bradzacher @controversial @kirkwaiblinger