Add 0.14.0 release to instant CHANGELOG #1272
Merged
Conversation
This file contains 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
🦋 Changeset detectedLatest commit: ed8b6a3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
brunoocasali
force-pushed
the
rollback-release
branch
from
336eaad to
2335919
Compare
brunoocasali
force-pushed
the
rollback-release
branch
from
2335919 to
ed8b6a3
Compare
brunoocasali
added a commit
that referenced
this pull request
Dec 26, 2023
Add 0.14.0 release to instant CHANGELOG
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.
First of all, sorry for the inconvenience.
But I will deprecate the v1.0.0 of the
@meilisearch/instant-meilisearchpackage. It shouldn't be done in the first place. The new versioning system (changesets) automatically bumped the version to a major due to the changelog change named "major". For some reason, it triggered a version raise to 1.0, which was incorrect.So, the steps that follow this PR are going to be:
@meilisearch/instant-meilisearch#v0.14.0.@meilisearch/instant-meilisearch#v1.0.0here on GitHub@meilisearch/instant-meilisearch#v1.0.0at npm.If you're a user from instant-meilisearch, you could safely migrate from v1.0.0 to v0.14.0. They are the same release with just the version change.
Why you folks don't keep it?
The integrations team is a really really small team that manages more than 30 different packages from SDKs to meilisearch tooling. Having a v1.0 package under our umbrella means that we should take extra care about everything we do, plus sometimes we are not even sure if that package could be considered "stable".
We bumped some of our integrations, like Meilisearch PHP, to v1 for external reasons. In any case, you should expect the same quality of maintenance here and in any other Meilisearch repo. Our goal is to make our tools easier and easier to adopt and not to raise any alarms when you upgrade them.
But as soon you put the semver to v1.0, that became a rule, not a good practice/mantra like it is today, and due to our small team, this could not be a rule yet.
Again, I apologize for the inconvenience and thanks for using Meilisearch ❤️!