graasp / .github Goto Github PK

    Would it make sense to factor out release please to our own actions registry at some point? So that we can set these default changelog-types, and add the possibility to overwrite the config?

Originally posted by @dialexo in graasp/graasp-app-text-input#68 (comment)

Should we refactor the release-please workflows with automatic tag follow into a composite in graasp-deploy ?

Related comment by @dialexo can be found here

Create a Github Action that parses package.json and ensures that it follows our conventions:

• check that the version of the dependencies values is always a fixed semver (regex is ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ from the semver spec). In particular, github:... and ranged semvers should not be allowed.
• check that name is name of repo
• check license
• check that resolutions is minimal, and that the versions are expected

It shoud prevent branches from being merged if the conditions are not met