🔨💚 Refactor release process: remove fetch-depth fr… #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces changes to streamline the release process and improve workflow configurations. The most notable updates include replacing inline release commands with a dedicated script, removing unnecessary
fetch-depthsettings in multiple workflows, and adding a robustrelease.shscript to handle releases with enhanced error handling and flexibility.Workflow Configuration Updates:
.github/workflows/1.bump-version.yml: Removed thefetch-depth: 0option from the checkout step to simplify the workflow configuration..github/workflows/3.update-changelog.yml: Similarly removed thefetch-depth: 0option from the checkout step in the changelog update workflow.Release Process Improvements:
.github/workflows/2.build-publish.yml: Replaced the inline command for creating a release with a call to the newly addedscripts/release.shscript for better modularity and maintainability.scripts/release.sh: Added a new script to manage the release process, including environment variable loading, error handling for missing dependencies (gitandgh), authentication checks, and support for optional build steps.