[BUG] install specific version of the Doppler CLI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 396
- Forks
- 83
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 3
Description
Describe the bug
Version v3.57.0 introduced a bug that forced us to change the doppler config because it made our CI fail (thus blocking all PRs).
We had to hotfix the config and we adopted the new monorepo feature introduced by this release.
Shortly after you released a v3.57.1 that removed this feature and made our CI fail again.
How can we force our CI to use the v3.57.0 and not the latest version?
We are using dopplerhq/cli-action@v2 and it doesn't seem to have an option to install a specific version of the doppler CLI.
That could be really useful, particularly if you frequently introduce breaking changes
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the dopplerhq/cli-action@v2 workflow action and how it installs the CLI version. Confirm how a caller could request v3.57.0 rather than the latest release, then verify that the action can install and use that pinned version in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100