Repository navigation
chore: bump every port to 1.6.3 - #127
Merged
Merged
Conversation
Patch release so the next Go module tag requires golang.org/x/net v0.61.0 (#126) instead of a version with open advisories. Python and Node 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
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.
Why
Patch release for the Go port. The module tag
go/v1.6.2requiresgolang.org/x/net v0.58.0, which carries the advisories cleared in #126 (GO-2026-6603 through GO-2026-6617). A consumer'sgo gettakes that as the minimum, and manifest-level scanners point at FlightRadarAPI as the source. Tagginggo/v1.6.3from amainthat includes #126 publishes a module whose requirements are clean.Python and Node carry no code change since 1.6.2, 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.2 → 1.6.3go/flightradarapi/doc.go:Version1.6.2 → 1.6.3nodejs/package.jsonandpackage-lock.json: 1.6.2 → 1.6.3, vianpm versionso the lock stays in step with the manifestOrder
Merge #126 first, then this. The release tag has to land on a commit that already carries the
x/netbump and thego 1.26.0directive, or the Go module published under 1.6.3 would be the same as 1.6.2.After merge
Publish the GitHub release
v1.6.3frommain. That triggers the publish workflow for PyPI, npm and thego/v1.6.3module tag. Note the Go module now needs Go 1.26 or newer on the consumer side.