actions/lint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-12-18 02:32:10 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
lint/docs/release-process.md
Marco Ferrari 170cabf92b
Some checks failed
Publish Images / Build and Test (push) Has been cancelled
Details
Build and Test / Set build metadata (push) Has been cancelled
Details
Build and Test / Build test suite matrix (push) Has been cancelled
Details
Build and Test / preview-release-notes (push) Has been cancelled
Details
Lint commit / commitlint (push) Has been cancelled
Details
Publish Images / Release (push) Has been cancelled
Details
Build and Test / Build and Test (push) Has been cancelled
Details
Build and Test / Test the Super-linter GitHub Action (push) Has been cancelled
Details
Build and Test / Run test cases (push) Has been cancelled
Details
Build and Test / Check if all the tests passed (push) Has been cancelled
Details
chore: devcontainer, docs, prettier config (#6119) 
- Update devcontainer by setting Prettier as a formatter only for
  supported languages.
- Install only the VS Code extensions that we need for Super-linter
  development.
- Remove the devcontainer as soon as it's not needed to avoid leaving
  leftovers behind.
- Enable proseWrap in Prettier configuration.
- Update documentation about how to configure new linters.
- Fix linting issues.
2024-09-13 14:37:48 +02:00

1.2 KiB
Raw Blame History

Super-Linter releases

The Process to create a super-linter release is as follows:

  1. Merge the release pull request.

Preview the release pull request

In order to have a preview of the next release before merging a pull request that updates the configuration of the tooling that we use to create releases, do the following:

  1. Run:

    make release-please-dry-run

This command also runs as part of the CI process.

Release workflows

Every push to the default branch triggers GitHub Actions workflows that:

  • Build and deploy of super-linter container images:

    • super-linter/super-linter:latest
    • super-linter/super-linter:slim-latest

  • Update the next release pull request.

Release automation tooling

In order to automate releases, we use release-please.

We configure release-please using two files: