frgfm/validate-python-headers - v0.5.1

This patch release removes unnecessary dependencies from the image which speeds up workflow initialization, and reduce memory footprint.

What's Changed

Improvements

• build(deps-dev): bump ruff from 0.5.5 to 0.5.6 by @dependabot in https://github.com/frgfm/validate-python-headers/pull/29
• build(deps-dev): switched from poetry to uv by @frgfm in https://github.com/frgfm/validate-python-headers/pull/46
• build(deps): bump actions/labeler from 4 to 5 by @dependabot in https://github.com/frgfm/validate-python-headers/pull/47
• ci(push): fix GHCR docker push by @frgfm in https://github.com/frgfm/validate-python-headers/pull/49
• build(deps): remove unnecessary deps by @frgfm in https://github.com/frgfm/validate-python-headers/pull/50

New Contributors

• @dependabot made their first contribution in https://github.com/frgfm/validate-python-headers/pull/23

Full Changelog: https://github.com/frgfm/validate-python-headers/compare/v0.5.0...v0.5.1

- Python
Published by frgfm about 1 year ago

frgfm/validate-python-headers - v0.5.0

This minor release improves the remediation message and speeds up the action.

Highlights

Better remediation :speaker:

When any header was invalid, we were showing you one of the accepted headers. Let's say you created a file in 2020, your organization is named Pyronear and you picked the Apache 2 license. Now we're in 2024, you would have received this message: ``` Your header should look like:

Copyright (C) 2023-2024, Pyronear.

This program is licensed under the Apache License 2.0.

this is not correctly updated to: Your header should look like:

Copyright (C) -2024, Pyronear.

This program is licensed under the Apache License 2.0.

```

Python 3.11 :zap:

We upgrade the python version from 3.8 to 3.11 for the action's docker which should save you some CI minutes!

What's Changed

New Features 🚀

• style(ruff): switched from flake8, isort, bandit & black to ruff by @frgfm in https://github.com/frgfm/validate-python-headers/pull/18 ### Improvements
• fix(src): update the suggestion when headers are invalid by @frgfm in https://github.com/frgfm/validate-python-headers/pull/20
• perf(docker): bump python from 3.8 to 3.11 by @frgfm in https://github.com/frgfm/validate-python-headers/pull/21
• docs(readme): update the message example by @frgfm in https://github.com/frgfm/validate-python-headers/pull/22

Full Changelog: https://github.com/frgfm/validate-python-headers/compare/v0.4...v0.5.0

- Python
Published by frgfm over 1 year ago

frgfm/validate-python-headers - v0.4: Adds a new option for custom license notice

This minor release adds the possibility to have a custom license notice.

Highlights

Custom license notice :shushing_face:

When developing software, you might sometimes not be able to share your work in open source. This is understandable and implies that you have a custom license notice. This release allows you to do so:

uses: frgfm/validate-python-headers@main with: owner: 'François-Guillaume Fernandez' starting-year: 2022 license-notice: '.github/license-notice.txt' ignore-folders: '.github/'

Enjoy!

What's Changed

New Features 🚀

• feat: Adds possibility to have a custom license notice by @frgfm in https://github.com/frgfm/validate-python-headers/pull/15 ### Improvements
• ci: Adds a test case in the CI by @frgfm in https://github.com/frgfm/validate-python-headers/pull/16

Full Changelog: https://github.com/frgfm/validate-python-headers/compare/v0.3...v0.4

- Python
Published by frgfm about 3 years ago

frgfm/validate-python-headers - v0.3: Adds a new option to ignore folders

This minor release adds the possibility to ignore folders & renames a previous option.

Highlights

Folder ignoring :seenoevil:

Until now you could ignore files, but let's be honest: most tools allow you to ignore folders. While patterns are not supported yet, one feature was added to ignore entire folders:

uses: frgfm/validate-python-headers@main with: license: 'Apache-2.0' owner: 'François-Guillaume Fernandez' starting-year: 2022 ignore-folders: '.github/'

Enjoy!

Tighter cleaning :broom:

In order to improve the quality of the project, the following tools were added: - autoflake: to automatically apply flake8 - bandit: spots vulnerabilities in the code

Additionally, precommit hooks were added to minimize the forth-and-forth with the CI and have clean commits upfront :smile:

Breaking changes

Renamed parameter

The ignores option was renamed into ignore-files to have a more explicit naming and better align with new features. The following action:

uses: frgfm/validate-python-headers@main with: license: 'Apache-2.0' owner: 'François-Guillaume Fernandez' starting-year: 2022 ignores: '__init__.py,version.py' now needs to be modified as follows if you use the latest version: uses: frgfm/validate-python-headers@main with: license: 'Apache-2.0' owner: 'François-Guillaume Fernandez' starting-year: 2022 ignore-files: '__init__.py,version.py'

What's Changed

Breaking Changes 🛠

• feat: Adds the option to ignore folders by @frgfm in https://github.com/frgfm/validate-python-headers/pull/11 ### New Features 🚀
• ci: Adds Sponsor button by @frgfm in https://github.com/frgfm/validate-python-headers/pull/14 ### Bug Fixes 🐛
• docs: Fixes README typo by @frgfm in https://github.com/frgfm/validate-python-headers/pull/13 ### Improvements
• style: Adds autoflake, bandit & precommit by @frgfm in https://github.com/frgfm/validate-python-headers/pull/12

Full Changelog: https://github.com/frgfm/validate-python-headers/compare/v0.2...v0.3

- Python
Published by frgfm about 3 years ago

frgfm/validate-python-headers - v0.2: Added support for all SPDX licenses

This minor release fixes the Docker orchestration of the action and adds support for all SPDX-referenced licenses.

Highlights

Broad support of licenses :book:

Instead of manually adding the reference for all licenses, this release adds support for all SPDX-referenced licenses using their identifier. This should help for various projects with their own license requirements.

Minimal effort, insightful report :nerd_face:

The action was designed to have minimal input from the user, as shown below: uses: frgfm/validate-python-headers@main with: license: 'Apache-2.0' owner: 'François-Guillaume Fernandez' starting-year: 2022 ignores: 'version.py,__init__.py'

Using this in your workflow will allow you to have a wary assistant for your headers :raised_hands:

What's Changed

New Features 🚀

• feat: Extended supported licenses by @frgfm in https://github.com/frgfm/validate-python-headers/pull/9 ### Bug Fixes 🐛
• docs: Updated README by @frgfm in https://github.com/frgfm/validate-python-headers/pull/2
• fix: Fixed the Dockerfile and updated README by @frgfm in https://github.com/frgfm/validate-python-headers/pull/3
• fix: Fixed entrypoint by @frgfm in https://github.com/frgfm/validate-python-headers/pull/4
• fix: Fixed Dockerfile orchestration by @frgfm in https://github.com/frgfm/validate-python-headers/pull/5
• fix: Fixed entrypoint of the action Docker by @frgfm in https://github.com/frgfm/validate-python-headers/pull/6
• fix: Fixed validation script path by @frgfm in https://github.com/frgfm/validate-python-headers/pull/7
• fix: Fixed workdir access to the script by @frgfm in https://github.com/frgfm/validate-python-headers/pull/8 ### Improvements
• docs: Added contributing tools by @frgfm in https://github.com/frgfm/validate-python-headers/pull/10

Full Changelog: https://github.com/frgfm/validate-python-headers/compare/v0.1...v0.2

- Python
Published by frgfm over 3 years ago

frgfm/validate-python-headers - v0.1: Header validator for your Python files

This minor release provides a light GitHub action to check your Python headers for copyright and license notices.

Highlights

License check :heavycheckmark:

Using the license identifier, the action will automatically fetch the full license name and its URL so that your headers include all necessary mentions for your project to be correctly licensed.

Dynamic copyright year :hourglassflowingsand:

Complex projects have parts that have been designed years apart. This means that your code may have different starting copyright years and needs to be incorporated as such in the header. You only have to specific the starting year of your project, the action will take care of the rest :+1:

What's Changed

New Features 🚀

• feat: Added basic action setup by @frgfm in https://github.com/frgfm/validate-python-headers/pull/1

New Contributors

• @frgfm made their first contribution in https://github.com/frgfm/validate-python-headers/pull/1

Full Changelog: https://github.com/frgfm/validate-python-headers/commits/v0.1.0

- Python
Published by frgfm over 3 years ago