Repository navigation
chore(release): 0.4.0 - #30
Merged
Merged
Conversation
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.
Release metadata for 0.4.0. There is no issue to close.
What changed
package.jsonandpackage-lock.json: version0.3.4->0.4.0, written bynpm version 0.4.0 --no-git-tag-version. Only the three version fields change.CHANGELOG.md: the[Unreleased]entries are now## [0.4.0] - 2026-11-15, with an empty## [Unreleased]above it (same shape as the 0.3.4 release).README.md: the JSON report sample shows"version": "0.4.0". That field is the tool version (apigate.jssetsversion: pkg.version).No code, test or workflow changes.
What 0.4.0 ships
The entries merged since v0.3.4 (#19 to #22), listed under
## [0.4.0]in CHANGELOG.md. Changes users can notice: Node 18 is no longer supported (engines.nodeis>=20), and an exported Express router that no resolved mount reaches is now reportedUNRESOLVED(path: null, reasonmount-prefix-cross-file) instead of with a bare path.Proof
npm view @stelnyx/apigate versions: the newest published version is0.3.4, so0.4.0is free.git grep 0.3.4after the change finds only the[0.3.4]CHANGELOG heading and the provenance notes inREADME.mdandSECURITY.md, which refer to 0.3.4 on purpose.Gate at bfc1c50 (Node 24.22.1, npm 11.19.1)
npm ci: added 83 packages, found 0 vulnerabilitiesnpm run lint: cleannpm test: 20 suites, 256 passed, 0 failednpm pack --dry-run:@stelnyx/apigate@0.4.0, 26 files, 78.3 kBAfter merge
Tag
origin/mainasv0.4.0and push the tag (CONTRIBUTING.md, "Releases", step 4). The Publish workflow refuses a tag that does not match thepackage.jsonversion. The CHANGELOG date assumes the tag is pushed on 2026-11-15.