Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Don't publish new versions when nothing has changed #7521

Closed
Assignees
JamesHenry
Labels
repo maintenancethings to do with maintenance of the repo, and not with code/docs
@iebold

Description

@iebold

Suggestion

Hello,

I see according to your versioning policy fromhttps://main--typescript-eslint.netlify.app/users/versioning/ that

All of the packages in this project are published with the same version number to make it easier to coordinate both releases and installations.

I would suggest to reconsider this policy andnot do version bumps on packages just to keep them in sync.

typescript-eslint is constantly being updated by dependabot and the diffs are constantly the largest ones because you version bump all the packages which all get new version numbers /and/ package hashes.

This is a considerable waste in reviewing diffs plus a waste in pushing npm packages that are basically identical.

I personally don't see how this policy helps since npm takes care of everything and I don't see when one needs to "coordinate" installations and this would be a problem.

Metadata

Metadata

Assignees

Labels

repo maintenancethings to do with maintenance of the repo, and not with code/docs

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp