github-actions[bot] commented on PR #2895:
URL: https://github.com/apache/jackrabbit-oak/pull/2895#issuecomment-5140429417
# Commit-Check ❌
```
Commit rejected by Commit-Check.
(c).-.(c) (c).-.(c) (c).-.(c) (c).-.(c) (c).-.(c)
/ ._. \ / ._. \ / ._. \ / ._. \ / ._. \
__\( C )/__ __\( H )/__ __\( E )/__ __\( C )/__ __\( K )/__
(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)
|| E || || R || || R || || O || || R ||
_.' '-' '._ _.' '-' '._ _.' '-' '._ _.' '-' '._ _.' '-' '._
(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)
`-´ `-´ `-´ `-´ `-´ `-´ `-´ `-´ `-´ `-´
Commit rejected.
Type message check failed ==> Reapply "OAK-12193 Large numbers of deleted
Lucene documents cause trouble (#2873)"
This reverts commit 57a2b05bfdc2bff7370dc91ab448d27ed8610dbe.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 23/115:
Type message check failed ==> Revert "OAK-12227 Exclude Tika from oak-run
(#2919)"
This reverts commit 0f7edd5965dc5c23b169ad2ec11c531741a4ff94.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 25/115:
Type message check failed ==> [maven-release-plugin] prepare release
jackrabbit-oak-2.2.0
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 26/115:
Type message check failed ==> [maven-release-plugin] prepare for next
development iteration
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 27/115:
Type message check failed ==> Revert "[maven-release-plugin] prepare for
next development iteration"
This reverts commit f16bc60d0621dcf8edf1ca1a190bb399e653a921.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 28/115:
Type message check failed ==> Revert "[maven-release-plugin] prepare release
jackrabbit-oak-2.2.0"
This reverts commit 24564754ee94814f08550f6247916647e52ebd97.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 29/115:
Type message check failed ==> [maven-release-plugin] prepare release
jackrabbit-oak-2.2.0
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 30/115:
Type message check failed ==> Revert "[maven-release-plugin] prepare release
jackrabbit-oak-2.2.0"
This reverts commit d9842086fd758ce7df8ed5578d2dbfe51973b75d.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 31/115:
Type message check failed ==> [maven-release-plugin] prepare release
jackrabbit-oak-2.2.0
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 32/115:
Type message check failed ==> [maven-release-plugin] prepare for next
development iteration
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 46/115:
Type message check failed ==> Configure GitHub workflows to use concurrency
cancel-in-progress for
pull requests
see recommended best practices at Apache
https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=GitHub+Actions+Recommended+Practices
Signed-off-by: Aurélien Pupier <[email protected]>
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 47/115:
Type message check failed ==> Use Commit Check action version v2.7.0
(f237ed0085f49444ab5c85bdfa5cdcd490fc09c5)
The former version was not allow-listed by ASF in
https://github.com/apache/infrastructure-actions/blob/main/actions.yml
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 65/115:
Type message check failed ==> Revert "OAK-12281: Upgrade jackson-databind
dependency to 2.20.2 (#2976)"
This reverts commit 1aee3adee83ef87f1424af00da73f01f215dd538.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 66/115:
Type message check failed ==> oak-http: extract Authorization Field parsing
and add test coverage (#2981)
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 72/115:
Type message check failed ==> Merge pull request #2984 from apache/OAK-12287
OAK-12287: Update to Apache Parent POM to version 39
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 81/115:
Type message check failed ==> Revert "OAK-12295 : bump mongo-driver-sync to
5.3.1 (#3001)" (#3012)
This reverts commit 480eb1454028de792fe603b572def624b6a4cccd.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 83/115:
Type message check failed ==> [maven-release-plugin] prepare release
jackrabbit-oak-2.4.0
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 84/115:
Type message check failed ==> [maven-release-plugin] prepare for next
development iteration
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 85/115:
Type message check failed ==> Revert "[maven-release-plugin] prepare for
next development iteration"
This reverts commit 78c17b812acc51d6cda7a67f6288521e975d6595.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 86/115:
Type message check failed ==> Revert "[maven-release-plugin] prepare release
jackrabbit-oak-2.4.0"
This reverts commit 92860e0916a4628118b0584ab5005bc664ba749c.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 87/115:
Type message check failed ==> [maven-release-plugin] prepare release
jackrabbit-oak-2.4.0
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 88/115:
Type message check failed ==> [maven-release-plugin] prepare for next
development iteration
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 93/115:
Type message check failed ==> Add draft project security threat-model
document (#2923)
* Add draft project security threat-model document
Adds a draft project-level security threat-model document
(draft-THREAT-MODEL.md) at repo root, improving discoverability
for automated security scanners running against this repository.
The file follows the rubric format used by several other ASF
projects piloting security-model discoverability.
The "draft-" prefix signals this is a proposal for the PMC to
review, correct, or reject — not a finalised maintainer-blessed
model. Every claim carries a provenance tag (documented /
inferred / maintainer) so reviewers can see where each claim
originates; §14 collects open questions for the maintainers.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
* Revise threat model per PMC review (Java 17, trust-boundary/XXE, oak-http,
TarMK open)
Generated-by: Claude Code
---------
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 104/115:
Type message check failed ==> docs: wire threat model for agent
discoverability + rename to THREAT_MODEL.md (#3042)
Adds AGENTS.md (## Security pointer) + SECURITY.md wiring the
conventional AGENTS.md -> SECURITY.md -> THREAT_MODEL.md chain, and
renames the PMC-merged draft-THREAT-MODEL.md to the canonical
THREAT_MODEL.md (no longer a draft; matches the discoverable
convention). No model content changes.
Generated-by: Claude Code (Claude Opus 4.8)
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
--- Commit 108/115:
Type message check failed ==> Revert "OAK-12319 : bump commons-io to 2.22.0
(#3036)" (#3053)
This reverts commit edee3fb58817ceeb2e813a75bd51f336fa973709.
The commit message should follow Conventional Commits. See
https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
