Stirling-PDF/.github/workflows
Ludy 9e8c16f313
checks the compatibility of the licenses (#2844)
# Description of Changes

### What was changed
- An **automated license check** was integrated into the CI/CD workflow
(`build.yml` and `licenses-update.yml`).
- A new file, `allowed-licenses.json`, was added to explicitly define
the permitted licenses.
- The **Gradle build process** was updated to run `checkLicense` and
detect any non-compliant licenses.

### Why the change was made
- **Improved license compliance** to ensure only compatible licenses are
used.
- **Automated license validation** within the CI/CD workflow to detect
potential incompatibilities early.
- **Legal risk mitigation** by excluding problematic licenses like
**GPL-2.0 (without Classpath Exception)**.

### Any challenges encountered
- The **allowed license list had to be manually curated** to ensure all
relevant open-source libraries were covered.
- Some dependencies use **slightly different license names** (e.g.,
`"Apache License, Version 2.0"` vs. `"Apache-2.0"`), which needed to be
handled in the validation process.

---

## Checklist

### General

- [x] I have read the [Contribution
Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md)
- [x] I have read the [Stirling-PDF Developer
Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md)
(if applicable)
- [x] I have read the [How to add new languages to
Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/HowToAddNewLanguage.md)
(if applicable)
- [x] I have performed a self-review of my own code
- [x] My changes generate no new warnings

### Documentation

- [x] I have updated relevant docs on [Stirling-PDF's doc
repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/)
(if functionality has heavily changed)
- [ ] I have read the section [Add New Translation
Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/HowToAddNewLanguage.md#add-new-translation-tags)
(for new translation tags only)

### UI Changes (if applicable)

- [ ] Screenshots or videos demonstrating the UI changes are attached
(e.g., as comments or direct attachments in the PR)

### Testing (if applicable)

- [x] I have tested my changes locally. Refer to the [Testing
Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#6-testing)
for more details.
2025-02-03 10:13:02 +00:00
..
auto-labeler.yml
build.yml checks the compatibility of the licenses (#2844) 2025-02-03 10:13:02 +00:00
check_properties.yml Bump actions/setup-python from 5.3.0 to 5.4.0 (#2856) 2025-02-03 10:09:15 +00:00
codeql.yml-disabled
dependency-review.yml
licenses-update.yml checks the compatibility of the licenses (#2844) 2025-02-03 10:13:02 +00:00
manage-label.yml Bump crazy-max/ghaction-github-labeler from 5.1.0 to 5.2.0 (#2854) 2025-02-03 10:07:54 +00:00
multiOSReleases.yml Bump actions/setup-java from 4.6.0 to 4.7.0 (#2855) 2025-02-03 10:08:34 +00:00
PR-Demo-cleanup.yml Update PR-Demo-cleanup.yml (#2817) 2025-01-30 18:40:05 +00:00
PR-Demo-Comment.yml Bump actions/setup-java from 4.6.0 to 4.7.0 (#2855) 2025-02-03 10:08:34 +00:00
pre_commit.yml Bump actions/setup-python from 5.3.0 to 5.4.0 (#2856) 2025-02-03 10:09:15 +00:00
push-docker.yml Bump actions/setup-java from 4.6.0 to 4.7.0 (#2855) 2025-02-03 10:08:34 +00:00
releaseArtifacts.yml Bump actions/setup-java from 4.6.0 to 4.7.0 (#2855) 2025-02-03 10:08:34 +00:00
scorecards.yml Bump github/codeql-action from 3.28.6 to 3.28.8 (#2857) 2025-02-03 10:10:37 +00:00
stale.yml Bump actions/stale from 9.0.0 to 9.1.0 (#2803) 2025-01-30 10:43:17 +00:00
swagger.yml Bump actions/setup-java from 4.6.0 to 4.7.0 (#2855) 2025-02-03 10:08:34 +00:00
sync_files.yml Bump actions/setup-python from 5.3.0 to 5.4.0 (#2856) 2025-02-03 10:09:15 +00:00
testdriver.yml Bump actions/setup-java from 4.6.0 to 4.7.0 (#2855) 2025-02-03 10:08:34 +00:00