Adopt the updated repository policies
This commit is contained in:
@@ -1,9 +1,9 @@
|
||||
# Release Policy
|
||||
|
||||
**Base Policy Version:** 1.6
|
||||
**Base Policy Version:** 1.7
|
||||
|
||||
**Last Updated**: 2026-10-08
|
||||
**Upstream Source:** [Standard Repository Policies release](https://gitea.maximumdirect.net/eric/policy/src/commit/e833faddf120c789a9b45348edaf75720de16348/docs/policy/release.md)
|
||||
**Last Updated**: 2026-11-11
|
||||
**Upstream Source:** [Standard Repository Policies release](https://gitea.maximumdirect.net/eric/policy/src/commit/593c9b52273c5c879785ae9e995d21026df467b4/docs/policy/release.md)
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -82,6 +82,14 @@ For releases at or after `v1.0.0`:
|
||||
minimum as described below; and
|
||||
- a patch release may make backward-compatible fixes.
|
||||
|
||||
In this context, "backward-compatible" means only that pre-existing, valid
|
||||
configurations will continue to work following the release. Behavior need not
|
||||
remain strictly identical.
|
||||
|
||||
Audita's minor and patch releases also preserve the documented
|
||||
[subprocess integration](../integrations/subprocess.md) and
|
||||
[output-file](../integrations/output-files.md) contracts.
|
||||
|
||||
Before `v1.0.0`, a minor release may change a documented public, operational,
|
||||
configuration, data, integration, or compatibility contract when the release
|
||||
note explains the impact and required consumer action. A patch release must
|
||||
|
||||
Reference in New Issue
Block a user