This is an automated email from the ASF dual-hosted git repository.

lukaszlenart pushed a change to branch WW-5631-chaining-require-annotations
in repository https://gitbox.apache.org/repos/asf/struts.git


    omit a1740a45c WW-5631 test(chaining): cover fail-closed introspection; 
clarify target==action
    omit fe798b638 WW-5631 docs(chaining): document 
struts.chaining.requireAnnotations
    omit 7db36c9b4 WW-5631 test(chaining): cover includes interaction and 
proxied target
    omit b1b7aa1b3 WW-5631 refactor(chaining): align requireAnnotations parsing 
with BooleanUtils
    omit b8dd03654 WW-5631 feat(chaining): enforce @StrutsParameter on target 
when opted in
    omit 6970a3b2a WW-5631 test(chaining): add failing @StrutsParameter 
enforcement tests
    omit 90368eda3 WW-5631 test(chaining): add annotated/unannotated chaining 
fixtures
    omit bdc9a6581 WW-5631 feat(chaining): default 
struts.chaining.requireAnnotations=false
    omit b6128b64c WW-5631 feat(chaining): add 
struts.chaining.requireAnnotations constant
    omit 5560633d3 WW-5631 docs(chaining): add design spec and implementation 
plan
     add 6dbe7ab5a WW-5631 feat(chaining): add 
struts.chaining.requireAnnotations constant
     add c95155526 WW-5631 feat(chaining): default 
struts.chaining.requireAnnotations=false
     add ddc38e358 WW-5631 test(chaining): add annotated/unannotated chaining 
fixtures
     add 4fa2782b3 WW-5631 test(chaining): add failing @StrutsParameter 
enforcement tests
     add ca36a7d46 WW-5631 feat(chaining): enforce @StrutsParameter on target 
when opted in
     add 2fcae6c77 WW-5631 refactor(chaining): align requireAnnotations parsing 
with BooleanUtils
     add 7d9129529 WW-5631 test(chaining): cover includes interaction and 
proxied target
     add 52995f882 WW-5631 docs(chaining): document 
struts.chaining.requireAnnotations
     add ab5b25f7f WW-5631 test(chaining): cover fail-closed introspection; 
clarify target==action

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (a1740a45c)
            \
             N -- N -- N   refs/heads/WW-5631-chaining-require-annotations 
(ab5b25f7f)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 ...ning-interceptor-strutsparameter-enforcement.md | 669 ---------------------
 ...terceptor-strutsparameter-enforcement-design.md | 164 -----
 2 files changed, 833 deletions(-)
 delete mode 100644 
docs/superpowers/plans/2026-05-27-WW-5631-chaining-interceptor-strutsparameter-enforcement.md
 delete mode 100644 
docs/superpowers/specs/2026-05-27-chaining-interceptor-strutsparameter-enforcement-design.md

Reply via email to