Skip to content

Feature/v1.2.0#23

Closed
PasinduOG wants to merge 3 commits intomainfrom
feature/v1.2.0
Closed

Feature/v1.2.0#23
PasinduOG wants to merge 3 commits intomainfrom
feature/v1.2.0

Conversation

@PasinduOG
Copy link
Contributor

No description provided.

…Check

BREAKING CHANGE: Security features now require explicit opt-in via field annotations

Major Changes:
- Introduced @AutoTrim annotation for opt-in whitespace trimming
- Introduced @XssCheck annotation for opt-in XSS validation
- Removed @notrim annotation (no longer needed with opt-in approach)
- Changed default behavior: fields are NOT modified unless explicitly annotated

Migration Required:
Previously in v1.2.0, all string fields were automatically trimmed and XSS-validated.
In v1.3.0, you must explicitly annotate fields with @AutoTrim or @XssCheck.

Example:
```java
// Before (v1.2.0)
public class UserDTO {
    private String username;  // Was automatically trimmed
    private String comment;   // Was automatically XSS-validated
}

// After (v1.3.0) - Add annotations
public class UserDTO {
    @AutoTrim
    private String username;

    @XssCheck
    private String comment;
}
- Added -Dgpg.passphrase system property to the mvn deploy command in the GitHub Actions workflow.
- Resolves the "Unable to decrypt gpg passphrase" error during Maven Central deployment.
@PasinduOG PasinduOG closed this Feb 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant