chore: fix version in metadata and ship config

[JasonBerry]

Changes

• ship.config.js: Read version from package.json instead of using Ship.js's tag parameter (which is the npm dist-tag "latest", not the semver version)
• ship.config.js: Remove unwanted shouldPrepare block
• metadata.yaml: Fix 5 historical entries that had "latest" instead of actual version numbers, and remove v prefix for consistency

[jkaho]

Can you enlighten me as to why you say shouldPrepare is unused? I thought this config is used to block releases for chore and refactor commits, for example. At least that's what I got from looking at the shipjs source code.

[JasonBerry]

Can you enlighten me as to why you say shouldPrepare is unused? I thought this config is used to block releases for chore and refactor commits, for example. At least that's what I got from looking at the shipjs source code.

"Unused" is the wrong word to use there, "unwanted" would be more accurate. Any time search-insights is updated we'd want to be able to release a change, but that's typically a "chore" commit and the shouldPrepare was blocking us from being able to trigger a release after updating that package.

[jkaho]

We've got this script that runs a weekly release–wouldn't this change mean that refactors would also result in a release? Is this what we want? Could we skip preparation for just the refactors?

[JasonBerry]

We've got this script that runs a weekly release–wouldn't this change mean that refactors would also result in a release? Is this what we want? Could we skip preparation for just the refactors?

That script doesn't automatically release, it just creates a PR which you can choose to merge if you want to trigger the release, so we still have full control of when we want to release.

[jkaho]

Ah okay, thanks for clearing that up 👍