Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/verify-release-signing.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ env:
EXPECTED_GPG_FINGERPRINT: F6109A4F3F5616E1A7A62099E02DB03BAF6C438C
# Never released; the runner's copy of the POMs is set to it so the
# staging repository looks like a release, and nothing is pushed.
VERSION: 20000101.0
VERSION: '20000101.0'

jobs:
verify:
Expand Down
1 change: 1 addition & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,7 @@ Hard rules. Never violate them, never refactor around them.
- Match the surrounding code: 2-space indentation, no tabs, and the same header on every new file, including `SPDX-License-Identifier: Apache-2.0 OR BSD-2-Clause`.
- Record user-visible changes as a bullet under the `* Next release` heading at the top of `change_log.md`. The release workflow turns that heading into the release entry; do not add release headings or edit released entries.
- Releases are maintainer-driven. Do not modify the project version in any `pom.xml`, `SECURITY.md`, `docs/vulnerabilities.md`, `docs/maven.md`, `.github/workflows/release.yml`, or the JReleaser configuration in the parent `pom.xml`.
- In workflow YAML, quote every version and other value that must stay a string. Unquoted, `20000101.0` is a number and reaches the shell as `20000101`.

## Vulnerability Handling

Expand Down
Loading