Skip to content

Conversation

@mattfarina
Copy link
Member

The NewVersion function, which uses the loose parser, had the regex for detection updated based on the official one. A change was made to allow for versions like 1.2 and other "loose" ones (to use the node semver term).

StrictNewVersion had some internal validation updated to catch issues.

For NewVersion, the benchmarking is now faster than the previous regex.

Ref #211

The NewVersion function, which uses the loose parser, had the regex for
detection updated based on the official one. A change was made to allow
for versions like 1.2 and other "loose" ones (to use the node semver
term).

StrictNewVersion had some internal validation updated to catch issues.

For NewVersion, the benchmarking is now faster than the previous regex.

Ref Masterminds#211

Signed-off-by: Matt Farina <[email protected]>
@mattfarina mattfarina merged commit 1558ca3 into Masterminds:master Nov 19, 2024
13 checks passed
@mattfarina mattfarina deleted the fix-bad-versions branch November 19, 2024 20:00
tacdom pushed a commit to industrial-asset-hub/asset-link-sdk that referenced this pull request Nov 26, 2024
fix(deps): update module github.com/masterminds/semver/v3 to v3.3.1

This MR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [github.com/Masterminds/semver/v3](https://github.com/Masterminds/semver) | require | patch | `v3.3.0` -> `v3.3.1` |

---

### Release Notes

<details>
<summary>Masterminds/semver (github.com/Masterminds/semver/v3)</summary>

### [`v3.3.1`](https://github.com/Masterminds/semver/releases/tag/v3.3.1)

[Compare Source](Masterminds/semver@v3.3.0...v3.3.1)

#### What's Changed

-   Fix for allowing some version that were invalid by [@&#8203;mattfarina](https://github.com/mattfarina) in Masterminds/semver#253

**Full Changelog**: Masterminds/semver@v3.3.0...v3.3.1

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

:tools: with :heart: by the [DevOps Automation Bot](https://code.siemens.com/devops.automation)
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xNDIuNCIsInVwZGF0ZWRJblZlciI6IjM4LjE0Mi40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

See merge request common-device-management/shared/cdm-dcd-sdk!21

Merged-by: Swati Shinghal <[email protected]>
xoxys added a commit to thegeeklab/wp-plugin-go that referenced this pull request Dec 10, 2024
…115)

BREAKING CHANGE: Due to an upstream change in [Masterminds/semver](Masterminds/semver#253) versions like `22.04` are now invalid even when using with `strict: false`. Although this behavior is more correct, this change could lead to issues in some cases and require adjustments.

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Robert Kaussow <[email protected]>
@stefanprodan
Copy link

@mattfarina just a heads up that this changed released in a patch version v3.3.1 broke Flux, Argo and probably any other consumer of this package that deals with Helm charts. Turns out many Helm users don't actually follow semver and use a leading 0 on a number segment e.g. 2025.04.02, which now fails to parse. We decided to rollback to v3.3.0 in Flux: fluxcd/pkg#915

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants