Summary
In December 2021, we updated the LaunchDarkly Code References GitHub Action to use semantic versioning that matched the ld-find-code-refs CLI, starting with version 2.4.1.
This disrupted dependabot updates that you may have been using to keep the action up to date (See GitHub Issue 25).
Planned Changes
In order to resume automated updates and provide you with reliable and consistent updates, we will remove old version tags on January 9, 2023.
We are also changing the default branch of the repository from master to main. We will preserve the master branch until January 9, 2023.
If you are using the GitHub Action with the master branch we strongly recommend pinning to the latest version. If you have a specific version pinned, you don’t need to worry about the default branch update.
Update Guide
Update your GitHub Action using one of the following methods. If you do not update your GitHub Action, the LaunchDarkly GitHub Action will fail to complete.
Option 1:
We strongly encourage our customers to move to the latest version of the GitHub Action, which is currently v2.8.0.
Option 2:
If you prefer to stay on your current version you can switch to this new tag immediately.
- v14 -> v2.4.0
- v13 -> v2.4.0-rc.1
- v12 -> v2.2.2
- v11 -> v2.2.2-rc.2
- v10 -> v2.2.2-rc.1
- v9 -> v2.1.0
- v8 -> v2.0.1
- v7 -> v2.0.0
- v6 -> v1.5.0
- v5 -> v1.4.0
- v4 -> v1.4.0-rc.1
- v3 -> v1.3.0
- v2 -> v1.2.0
- v1 -> v1.1.1
Customer Impact
We have identified a small number of customers may be affected by the GitHub Action version change. LaunchDarkly customers who are using the old version can avoid negative impacts by switching to the latest version of GitHub Actions or switching to the new semantic versioning.
We have already contacted affected customers, but if you’re one of them or would like help identifying whether you’re impacted by this change, you can open a support ticket and we’ll be glad to help out.