aquaproj/aqua (aquaproj/aqua)
### [`v2.25.0`](https://togithub.com/aquaproj/aqua/releases/tag/v2.25.0)
[Compare Source](https://togithub.com/aquaproj/aqua/compare/v2.24.1...v2.25.0)
[Pull Requests](https://togithub.com/aquaproj/aqua/pulls?q=is%3Apr+milestone%3Av2.25.0) | [Issues](https://togithub.com/aquaproj/aqua/issues?q=is%3Aissue+milestone%3Av2.25.0) | https://github.com/aquaproj/aqua/compare/v2.24.1...v2.25.0
##### Features
[#2749](https://togithub.com/orgs/aquaproj/discussions/2749#discussioncomment-8808062) [#2752](https://togithub.com/aquaproj/aqua/issues/2752) Support excluding some packages from the target of `aqua update`
e.g. aqua.yaml
```yaml
packages:
- name: golang/vuln/govulncheck@v1.0.3
update:
##### If enabled is false, aqua up command ignores the package.
##### If the package name is passed to aqua up command explicitly, enabled is ignored.
##### By default, enabled is true.
enabled: false
```
##### Fixes
[#2747](https://togithub.com/aquaproj/aqua/issues/2747) [#2354](https://togithub.com/aquaproj/aqua/issues/2354) [#2750](https://togithub.com/aquaproj/aqua/issues/2750) [#2751](https://togithub.com/aquaproj/aqua/issues/2751) Improve the logic to get the latest version
We've changed the logic to get the latest version in some commands such as `aqua update` and `aqua generate`.
The original logic was to call GitHub API `Get a latest release`, but a latest release wan't necessarily a latest version.
So we changed the logic to list the recent releases and get a latest version by semver.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v2.24.1->v2.25.0Release Notes
aquaproj/aqua (aquaproj/aqua)
### [`v2.25.0`](https://togithub.com/aquaproj/aqua/releases/tag/v2.25.0) [Compare Source](https://togithub.com/aquaproj/aqua/compare/v2.24.1...v2.25.0) [Pull Requests](https://togithub.com/aquaproj/aqua/pulls?q=is%3Apr+milestone%3Av2.25.0) | [Issues](https://togithub.com/aquaproj/aqua/issues?q=is%3Aissue+milestone%3Av2.25.0) | https://github.com/aquaproj/aqua/compare/v2.24.1...v2.25.0 ##### Features [#2749](https://togithub.com/orgs/aquaproj/discussions/2749#discussioncomment-8808062) [#2752](https://togithub.com/aquaproj/aqua/issues/2752) Support excluding some packages from the target of `aqua update` e.g. aqua.yaml ```yaml packages: - name: golang/vuln/govulncheck@v1.0.3 update: ##### If enabled is false, aqua up command ignores the package. ##### If the package name is passed to aqua up command explicitly, enabled is ignored. ##### By default, enabled is true. enabled: false ``` ##### Fixes [#2747](https://togithub.com/aquaproj/aqua/issues/2747) [#2354](https://togithub.com/aquaproj/aqua/issues/2354) [#2750](https://togithub.com/aquaproj/aqua/issues/2750) [#2751](https://togithub.com/aquaproj/aqua/issues/2751) Improve the logic to get the latest version We've changed the logic to get the latest version in some commands such as `aqua update` and `aqua generate`. The original logic was to call GitHub API `Get a latest release`, but a latest release wan't necessarily a latest version. So we changed the logic to list the recent releases and get a latest version by semver.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.