-
-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix uppercased env #3516
Fix uppercased env #3516
Conversation
Uh... Do you know which PR has introduced it? |
Lint fail is unrelated and seems to be caused by golangci update: https://ci.woodpecker-ci.org/repos/3780/pipeline/14125/30 |
I can take care in a dedicated PR if you like. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3516 +/- ##
==========================================
- Coverage 36.08% 36.06% -0.02%
==========================================
Files 229 229
Lines 15480 15483 +3
==========================================
- Hits 5586 5584 -2
- Misses 9488 9493 +5
Partials 406 406 ☔ View full report in Codecov by Sentry. |
This PR was opened by the [ready-release-go](https://github.com/woodpecker-ci/plugin-ready-release-go) plugin. When you're ready to do a release, you can merge this pull-request and a new release with version `2.4.1` will be created automatically. If you're not ready to do a release yet, that's fine, whenever you add more changes to `main` this pull-request will be updated. ## Options - [ ] Mark this version as a release candidate ## [2.4.1](https://github.com/woodpecker-ci/woodpecker/releases/tag/2.4.1) - 2024-03-20 ### 🔒 Security - Only allow to deploy from push, tag and release [[#3522](#3522)] ### 🐛 Bug Fixes - Exclude setup from cli command exec. [[#3523](#3523)] - Fix uppercased env [[#3516](#3516)] - Fix env schema [[#3514](#3514)] ### Misc - Temp pin golangci version in makefile [[#3520](#3520)] --------- Co-authored-by: qwerty287 <[email protected]> Co-authored-by: 6543 <[email protected]>
closes #3515
I think after this is fixed, we should publish a new release as this can be quite important.