mirror of
https://github.com/Unleash/unleash.git
synced 2025-01-11 00:08:30 +01:00
73d13a07c7
Use the tag created by the build action when running npm version, otherwise the checkout actions gets the HEAD of the commit that triggered the original workflow resulting in the usage of the previous version. Potentially in the future, instead of triggering the build manually we could consider using the tag as a trigger for the build process and then all the dependent workflows should work fine. It's good we have this manual for validation, and we workaround some of the limitations before we invest more into more automation |
||
|---|---|---|
| .. | ||
| add-to-project.yml | ||
| auto-assign-pr-author.yaml | ||
| build_coverage.yaml | ||
| build_doc_prs.yaml | ||
| build_frontend_prs.yml | ||
| build_prs_jest_report.yaml | ||
| build.yaml | ||
| check_links.yaml | ||
| codeql-analysis.yml | ||
| dependency-review.yml | ||
| docker_publish.yaml | ||
| e2e.frontend.yaml | ||
| flag-no-response.yaml | ||
| generate-docs.yaml | ||
| gradual-strict-null-checks.yml | ||
| notify_enterprise.yaml | ||
| pr_add_test_results.yaml | ||
| publish-new-version.yaml | ||
| release_changelog.yml | ||
| release.yaml | ||
| reset_heroku.yml | ||
| update_contributors.yaml | ||
| update_version_for_version_checker.yml | ||
| validate-migrations.yaml | ||