Skip to content

fix: check for helm secrets version and update it #1927

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

Merged
merged 4 commits into from
Feb 13, 2025
Merged

Conversation

ElderMatt
Copy link
Contributor

This PR updates the helm secrets package to the correct version for local use

Copy link

github-actions bot commented Feb 5, 2025

Coverage report

St.
Category Percentage Covered / Total
🔴 Statements
47.44% (+0.11% 🔼)
900/1897
🔴 Branches
27.87% (+0.49% 🔼)
170/610
🔴 Functions
39.51% (+0.41% 🔼)
96/243
🔴 Lines
46.53% (+0.12% 🔼)
785/1687

Test suite run success

63 tests passing in 8 suites.

Report generated by 🧪jest coverage report action from 95c931f

@CasLubbers
Copy link
Contributor

Was also thinking about the issue you had. In the apl-core code for encrypt/decrypt it's maybe better to check if the library is there otherwise give an error.

@ElderMatt
Copy link
Contributor Author

That would also be a good addition. Perhaps we can run a couple of check before running npm run server, npm bootstrap-dev or npm run bootstrap-dev-with-repo for example.

@merll merll merged commit b74377c into main Feb 13, 2025
8 checks passed
@merll merll deleted the fix-update-secrets-deps branch February 13, 2025 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants