Add script for updating package version

[flevi29]

Pull Request

What does this PR do?

• adds a script which assists in updating the version of this package
• the command is yarn update-version
• arguments are one of
  • -p (or --patch or no arguments) - bumps the patch version (0.46.0 -> 0.46.1)
  • -m (or --minor) - bumps the minor version (0.46.0 -> 0.47.0)
  • -M (or --major) - bumps the major version (0.46.0 -> 1.0.0)
  • -e (or --exact) - changes the version to exactly what you specify as X.X.X

PR checklist

Please check if your PR fulfills the following requirements:

• Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
• Have you read the contributing guidelines?
• Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.81%. Comparing base (756d856) to head (f6943f3).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1794   +/-   ##
=======================================
  Coverage   97.81%   97.81%           
=======================================
  Files          17       17           
  Lines        1465     1465           
  Branches      307      307           
=======================================
  Hits         1433     1433           
  Misses         32       32           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[flevi29]

Or would you prefer changeset, like in meilisearch-js-plugins?

[flevi29]

I can see that there's an automatic script that already makes a PR for this. How does it work?
#1797
Couldn't figure out how the bot knows what to update.

[Strift]

Hey @flevi29, thanks for your contribution.

The automation used for creating the PR you mentioned lives in a private repository. It's a bit old, but it's working for now, so I think @curquiza prefers not to touch it for now.

[flevi29]

@Strift Ah okay, I made this PR because CONTRIBUTING.md states that the version is updated manually. If #1792 ever becomes a reality, this private repository you mentioned will have to be updated. Unless JSR starts supporting package.json, which honestly they should (just opened an issue, let's see their reasoning jsr-io/jsr#864), but it's not a big deal to update an additional JSON file.

I guess I'm closing this then.

[curquiza]

@flevi29 yes so far, the automation is private

However, I would be ok to add an automation here, but only as a github action (with workflow dispatch`). I don't want we need to go in the terminal and run a script to do it. Everything in the GitHub interface will be better 😉

[flevi29]

Alright, I'll think about it that way. 👍

[flevi29]

Hey @curquiza, I see these types of PRs: #1830

What is the trigger for them? They can't be automatic, right? They have to be manually run workflows, right?

Also I somehow need to get the version from release drafter? How does the current implementation solve it?