chore: release v2.2.3 - #210
Merged
Merged
Conversation
The v2.2.3 tag was pushed onto the PR #209 merge commit while package.json still read 2.2.2, so npm rejected the publish with "You cannot publish over the previously published versions: 2.2.2". Bump package.json to 2.2.3 and close the Unreleased changelog section. Also add a pre-flight step to the publish workflow that compares the git tag against package.json before npm ci / tests / audit run, so a future mismatch fails in seconds with an actionable message instead of surfacing as a registry error at the dry-run step. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Проблема
Публикация Publish #32558957627 упала на шаге
Verify package contents:Тег
v2.2.3был повешен на мердж-коммит PR #209 (10607cc), гдеpackage.jsonвсё ещё содержал"version": "2.2.2". Версия 2.2.2 уже опубликована в npm 2026-08-14, поэтому реестр отклонил повторную публикацию.Пропущен принятый в репозитории шаг: сначала отдельный коммит
chore: release vX.Y.Z, поднимающий версию (как5375889для 2.2.2), и только потом тег на него.Изменения
package.json:2.2.2→2.2.3.CHANGELOG.md: секция## Unreleased(содержимое PR fix: separate crawlers from apps that merely name the vendor #209) закрыта как## 2.2.3 - 2026-08-22..github/workflows/publish.yml: новый шагVerify tag matches package versionсразу послеSetup Node.js. СверяетGITHUB_REF_NAMEс версией вpackage.jsonдоnpm ci/тестов/аудита — расхождение теперь падает за секунды с внятным сообщением, а не всплывает как ошибка реестра на dry-run.Проверка
npm ci— 0 vulnerabilitiesnpm test— 13 файлов, 201 тест, все зелёныеnpm audit --audit-level=high— 0 vulnerabilitiesnpm publish --dry-run—+ express-useragent@2.2.3, без ошибки о перезаписи версииv9.9.9vs2.2.3, пропускаетv2.2.3После мержа
Тег
v2.2.3нужно перевесить на релизный коммит вmaster— сейчас он указывает на10607cc.🤖 Generated with Claude Code