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

Appearance settings

Keep only major.minor in Processor#version#2109

Open
MahinAnowar wants to merge 1 commit into
postcss:mainpostcss/postcss:mainfrom
MahinAnowar:version-major-minorMahinAnowar/postcss:version-major-minorCopy head branch name to clipboard
Open

Keep only major.minor in Processor#version#2109
MahinAnowar wants to merge 1 commit into
postcss:mainpostcss/postcss:mainfrom
MahinAnowar:version-major-minorMahinAnowar/postcss:version-major-minorCopy head branch name to clipboard

Conversation

@MahinAnowar

Copy link
Copy Markdown
Contributor

Fixes #2101

Processor#version now holds only major.minor ('8.5'), so patch releases no longer require the manual lib/processor.js sync (the repo is currently on the 8.5.16 tag while the file said 8.5.15 — exactly the chore this removes).

Details:

  • The only functional consumer, the plugin-compatibility warning in lib/lazy-result.js, already compares just split('.')[0]/[1], so it works unchanged with a two-segment version.
  • test/version.js still guards against drift: it now compares Processor#version against package.json's major.minor, so a minor/major bump without updating lib/processor.js still fails CI, while patch releases no longer trip it.
  • Updated the two format assertions (test/processor.test.ts, test/postcss.test.ts) to /^\d+\.\d+$/ — they fail on the previous three-segment value and pass now — and the Processor#version JSDoc.

All checks pass locally: 652/652 unit tests, lint, types, version guard.

@ai

ai commented Jul 5, 2026

Copy link
Copy Markdown
Member

We haven’t started v9 branch yet.

I can keep your PR until we will start v9 development, but you need to fix merge conflict.

@MahinAnowar
MahinAnowar force-pushed the version-major-minor branch from 984730e to 504e8f1 Compare July 5, 2026 12:15
@MahinAnowar

Copy link
Copy Markdown
Contributor Author

Rebased onto main and resolved the conflict — kept '8.5' over the new 8.5.16 bump (the version guard now checks against package.json's major.minor, so it stays green). Happy to have this parked until v9 development starts.

@MahinAnowar
MahinAnowar force-pushed the version-major-minor branch 3 times, most recently from 7062542 to fd22449 Compare July 15, 2026 17:38
@MahinAnowar
MahinAnowar force-pushed the version-major-minor branch 2 times, most recently from 31a8f09 to 5a3314d Compare July 22, 2026 11:53
Hardcoding the full patch version forces a manual lib/processor.js edit
on every patch release. Only major.minor is ever consumed (lazy-result's
plugin compatibility warning), so store just that. The test/version.js
guard still catches drift against package.json on minor/major bumps.

Fixes postcss#2101
@MahinAnowar
MahinAnowar force-pushed the version-major-minor branch from 5a3314d to a9251e3 Compare July 25, 2026 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Put opnly major.minor in Processor.version

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.