fix(eslint-config): release the corrected dependencies manifest - #5
Open
losolio wants to merge 1 commit into
Open
fix(eslint-config): release the corrected dependencies manifest#5losolio wants to merge 1 commit into
losolio wants to merge 1 commit into
Conversation
npm's @eventuras/eslint-config@1.0.3 was published 2026-04-15 from the eventuras monorepo with all runtime packages in devDependencies, so consumers under pnpm's strict isolation cannot resolve @eslint/js and the other plugins at lint time. This repo already carries the corrected manifest (runtime packages in dependencies) but at the same version number, so changeset publish has been skipping it. A patch bump gets the fix out as 1.0.4. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a Changesets entry to force a patch release of @eventuras/eslint-config, so the already-corrected dependency manifest in this repo (runtime ESLint packages in dependencies) is actually published to npm as a newer version than the broken 1.0.3 tarball.
Changes:
- Add a changeset to bump
@eventuras/eslint-configfrom1.0.3→1.0.4(patch), enabling publication of the corrected manifest.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@eventuras/eslint-config@1.0.3on npm is the 2026-04-15 publish from the eventuras monorepo (libs/eslint-config), which declares every runtime package (@eslint/js,typescript-eslint, the plugins, …) indevDependencies. Under pnpm's strict isolation, any consumer outside that monorepo fails at lint time:This repo already carries the corrected manifest (runtime packages in
dependencies), but it kept version1.0.3— the same as the broken npm publish — sochangeset publishhas been silently skipping it. Hit while switching ratio-ui from its forked configs to the published@eventuras/*packages.Changes
@eventuras/eslint-config→ publishes the corrected manifest as1.0.4Note:
@eventuras/typescript-config@1.0.0on npm is also the old eventuras-monorepo publish, but it has no runtime dependencies and its presets match this repo's byte-for-byte (this repo addslibrary/nextjs/nodepresets on top), so it works as-is — worth a bump too at some point, but not blocking.🤖 Generated with Claude Code