Improve publish via CI + beta when in main

[nvuillam]

No description provided.

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ DOCKERFILE	hadolint	1		0	0.11s
✅ GROOVY	npm-groovy-lint	1	0	0	15.7s
✅ JAVASCRIPT	eslint	98	0	0	6.09s
✅ JSON	eslint-plugin-jsonc	9	0	0	2.25s
✅ JSON	jsonlint	9		0	0.37s
✅ JSON	npm-package-json-lint	yes		no	1.94s
✅ JSON	prettier	9	0	0	1.73s
✅ JSON	v8r	9		0	7.72s
✅ MARKDOWN	markdownlint	7	0	0	3.01s
✅ MARKDOWN	markdown-link-check	7		0	1.05s
✅ MARKDOWN	markdown-table-formatter	7	0	0	0.61s
✅ REPOSITORY	checkov	yes		no	13.78s
✅ REPOSITORY	gitleaks	yes		no	10.13s
✅ REPOSITORY	git_diff	yes		no	0.08s
✅ REPOSITORY	grype	yes		no	12.83s
✅ REPOSITORY	secretlint	yes		no	1.91s
✅ REPOSITORY	trivy-sbom	yes		no	1.15s
✅ REPOSITORY	trufflehog	yes		no	16.24s
✅ SPELL	cspell	121		0	9.39s
✅ SPELL	lychee	20		0	2.89s
✅ YAML	prettier	3	0	0	0.68s
✅ YAML	v8r	3		0	10.44s
✅ YAML	yamllint	3		0	0.29s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[nvuillam]

@stevenh I don't know if it can help you, but I refactored the release process , now:

• master has been renamed into main
• Every new commit in main will generate a new beta (npm package + docker image) via CI
• Github releases will handle the official releases via CI

[djukxe]

Hi @nvuillam
Will it be effective only from next commit because I couldn’t find beta release after you merge this PR.

[nvuillam]

@djukxe it is already effective :)

https://www.npmjs.com/package/npm-groovy-lint/v/11.1.2-beta202310250645.0

npm i npm-groovy-lint@beta -g :)

[djukxe]

@djukxe it is already effective :)

https://www.npmjs.com/package/npm-groovy-lint/v/11.1.2-beta202310250645.0

npm i npm-groovy-lint@beta -g :)

works great, thanks for the command