Skip to content

switch back to releas version of jbang#14776

Merged
koppor merged 1 commit into
mainfrom
jbang
Jan 1, 2026
Merged

switch back to releas version of jbang#14776
koppor merged 1 commit into
mainfrom
jbang

Conversation

@Siedlerchr

@Siedlerchr Siedlerchr commented Jan 1, 2026 •
edited by qodo-free-for-open-source-projects Bot
Loading

Copy link
Copy Markdown
Member

User description

Closes #14739

Steps to test

Mandatory checks

  • I own the copyright of the code submitted and I license it under the MIT license
  • [.] I manually tested my changes in running JabRef (always required)
  • [.] I added JUnit tests for changes (if applicable)
  • [.] I added screenshots in the PR description (if change is visible to the user)
  • [.] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
  • [.] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

PR Type

Enhancement

Description

  • Switch from custom jbang-gradle-plugin to official dev.jbang plugin version 0.4.0

  • Remove workaround for upstream jbang-gradle-plugin issue

  • Fix minor formatting issue in build script

Diagram Walkthrough

flowchart LR
  A["Custom jbang-gradle-plugin<br/>workaround"] -- "upgrade to" --> B["Official dev.jbang<br/>v0.4.0"]
  C["Formatting issue"] -- "fix" --> D["Clean code"]
Loading

File Walkthrough
Relevant files
Dependencies
build.gradle.kts
Update jbang plugin to official release version                   

jablib/build.gradle.kts

 +2/-4     

@Siedlerchr Siedlerchr added the automerge PR is tagged with that label will be merged if workflows are green label Jan 1, 2026
@koppor koppor enabled auto-merge January 1, 2026 22:31
@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jan 1, 2026

Copy link
Copy Markdown
Contributor

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🟡
🎫 #13109
🔴 Make the `org.jabref.logic.pseudonymization.Pseudonymization` class available on the CLI
Provide a similar CLI experience to the consistency check
Implement the CLI functionality similar to the `org.jabref.cli.CheckConsistency` class
Codebase Duplication Compliance
⚪
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules
Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jan 1, 2026

Copy link
Copy Markdown
Contributor

PR Code Suggestions ✨

No code suggestions found for the PR.

@Siedlerchr Siedlerchr changed the title switch back to releas version of jabang switch back to releas version of jbang Jan 1, 2026
@koppor koppor added this pull request to the merge queue Jan 1, 2026
Merged via the queue into main with commit 4da1e26 Jan 1, 2026
84 of 96 checks passed
@koppor koppor deleted the jbang branch January 1, 2026 23:11
@github-actions github-actions Bot mentioned this pull request Jan 1, 2026
Closed
@Siedlerchr Siedlerchr mentioned this pull request Jan 12, 2026
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jabref-machine jabref-machine jabref-machine approved these changes

Assignees

No one assigned

Labels

automerge PR is tagged with that label will be merged if workflows are green Review effort 1/5

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Switch to release of jbang-gradle-plugin

3 participants

@Siedlerchr @jabref-machine @koppor