Repository navigation
chore: bump every port to 1.6.2 - #125
Merged
Merged
Conversation
Patch release so the published npm manifest carries the undici ^6.29.0 floor from #123. Python and Go move with it because verify-versions refuses a release whose three declared versions disagree.
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.
Why
Patch release for the Node port. The
flightradarapi1.6.1 published on npm still declaresundici: ^6.28.0, a floor that admits a version hit by three high-severity advisories (GHSA-3wwx-pv8p-q78v, GHSA-r53p-7pc4-xj5r, GHSA-rfgv-xxqx-mfg5). #123 raised the floor to^6.29.0onmain; this bump gets that manifest onto the registry sonpm auditand Dependabot on consumers see a clean package instead of a transitive fix.Python and Go carry no code change since 1.6.1, but the three declared versions have to agree or
verify-versionsrefuses the release, so they move together.What
python/FlightRadarAPI/__init__.py:__version__1.6.1 → 1.6.2go/flightradarapi/doc.go:Version1.6.1 → 1.6.2nodejs/package.jsonandpackage-lock.json: 1.6.1 → 1.6.2, vianpm versionso the lock stays in step with the manifestAfter merge
Publish the GitHub release
v1.6.2frommain. That triggers the publish workflow for PyPI, npm and thego/v1.6.2module tag.