Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: v6.2.0 release preparation #1891

Closed
wants to merge 2 commits into from
Closed

Conversation

JaffaKetchup
Copy link
Member

@JaffaKetchup JaffaKetchup commented May 26, 2024

Readers: see https://docs.fleaflet.dev/getting-started/v7-information for info.

Cherry picked from commit 4f6b524, with minor changes to prepare for release.

DO NOT MERGE. Exists for the purpose of transparency only. v7 will be released simultaneously.

@JaffaKetchup

This comment was marked as outdated.

@JaffaKetchup JaffaKetchup deleted the v6.2.0-release-prep branch May 26, 2024 20:56
@josxha josxha restored the v6.2.0-release-prep branch May 27, 2024 17:53
@JaffaKetchup JaffaKetchup deleted the v6.2.0-release-prep branch May 27, 2024 21:33
@JaffaKetchup
Copy link
Member Author

Information for readers:

Due to a complex release of v6.1.0, we used a seperate branch, much like this release, and cherry picked the necessary commits. That branch was #1741.
However, due to an oversight when releasing v6.2.0, rather than merging cherry picks into a branch based off the last commit of #1741, instead it used commit ec81782, to create branch #1891
This commit included a history of some breaking changes.
This meant that v6.2.0 was inadvertently released with these breaking changes, meaning it caused projects to fail to resolve when the otherwise valid constraint of ^6.0.0 was used.
The issue has been resolved in #1893, and has been released as v6.2.1, so all projects should resolve dependencies normally, without intervention, again.
The faulty version v6.2.0 has been retracted from pub.dev to prevent accidental dependency on it, and the also incorrect tag and release for v6.1.0 and v6.2.0 has been removed from GitHub.

@muhammadAtZealtouch

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants