-
Notifications
You must be signed in to change notification settings - Fork 190
Insights: zarf-dev/zarf
Overview
Could not load contribution data
Please try again later
7 Pull requests merged by 2 people
-
chore(deps): bump github.com/fluxcd/source-controller/api from 1.6.0 to 1.6.1
#3939 merged
Jun 24, 2025 -
chore(deps): bump github.com/derailed/k9s from 0.40.5 to 0.50.6
#3820 merged
Jun 23, 2025 -
feat(deploy): support for package namespace override flag
#3889 merged
Jun 23, 2025 -
chore(deps): bump github.com/fluxcd/pkg/apis/meta from 1.12.0 to 1.13.0
#3936 merged
Jun 23, 2025 -
chore(deps): bump the k8s group across 1 directory with 5 updates
#3933 merged
Jun 20, 2025 -
chore(deps): bump the cosign-providers group across 1 directory with 3 updates
#3931 merged
Jun 19, 2025 -
chore(deps): bump github.com/sergi/go-diff from 1.3.2-0.20230802210424-5b0b94c5c0d3 to 1.4.0
#3899 merged
Jun 18, 2025
7 Pull requests opened by 5 people
-
release: fix RC release process
#3919 opened
Jun 18, 2025 -
fix: allow access token to be used with `zarf package mirror-resources`
#3920 opened
Jun 18, 2025 -
chore(deps): bump github.com/pterm/pterm from 0.12.79 to 0.12.81
#3932 opened
Jun 19, 2025 -
chore: wrap mutex around appending to failed repository updates
#3934 opened
Jun 21, 2025 -
feat: add arch variable to variables
#3935 opened
Jun 21, 2025 -
feat: ZEP-0032 support ipv6 only
#3938 opened
Jun 23, 2025 -
chore(deps): bump github.com/anchore/stereoscope from 0.1.4 to 0.1.5
#3940 opened
Jun 24, 2025
3 Issues closed by 3 people
-
Setting --plain-http, but pods still try https
#3937 closed
Jun 23, 2025 -
Ability to control deploy-to namespace using a Zarf Variable
#2407 closed
Jun 23, 2025 -
Nodeport ZEP
#3923 closed
Jun 18, 2025
11 Issues opened by 3 people
-
CI test continuous improvement
#3930 opened
Jun 18, 2025 -
e2e and unit testing strategy
#3929 opened
Jun 18, 2025 -
Nightly Build
#3928 opened
Jun 18, 2025 -
Constant and variables replacement values
#3927 opened
Jun 18, 2025 -
Data Injection Refactor
#3926 opened
Jun 18, 2025 -
Fix Dynamic Nodeport Problem
#3925 opened
Jun 18, 2025 -
Improve Nodeport Security
#3924 opened
Jun 18, 2025 -
Nodeport functionality and security
#3922 opened
Jun 18, 2025 -
Stable v1 Schema
#3921 opened
Jun 18, 2025 -
Repo name mismatch after mutation
#3918 opened
Jun 18, 2025 -
Choosing 'auth' as ZarfPackageConfig component name will break deploy
#3917 opened
Jun 17, 2025
19 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
feat: track progress on image pull/push
#3904 commented on
Jun 23, 2025 • 12 new comments -
chore(deps): bump helm.sh/helm/v3 from 3.17.3 to 3.18.3
#3916 commented on
Jun 20, 2025 • 0 new comments -
chore(deps): bump github.com/docker/cli from 28.1.1+incompatible to 28.2.2+incompatible
#3879 commented on
Jun 24, 2025 • 0 new comments -
feat: add checking in remote repo if manifest is a chart
#3811 commented on
Jun 23, 2025 • 0 new comments -
Mirror Resources No Longer Authenticates with External GitLab Registry
#3915 commented on
Jun 23, 2025 • 0 new comments -
FluxCD helm release fails when using ocirepo resource as chart reference
#3435 commented on
Jun 21, 2025 • 0 new comments -
Change the `--timeout` flag to time the entire deployment rather than a single helm install / upgrade
#2962 commented on
Jun 18, 2025 • 0 new comments -
The Zarf agent should not mutate git repos when there was no git repo specified on Zarf init
#2740 commented on
Jun 18, 2025 • 0 new comments -
Remove SGET support from Cosign
#2761 commented on
Jun 18, 2025 • 0 new comments -
Canonicalized Media Types
#2705 commented on
Jun 18, 2025 • 0 new comments -
Signed releases
#2704 commented on
Jun 18, 2025 • 0 new comments -
Refactor `charts` definition in `zarf.yaml`
#2245 commented on
Jun 18, 2025 • 0 new comments -
Improve Zarf's backwards compatibility rules
#2036 commented on
Jun 18, 2025 • 0 new comments -
Support schema versioning and deprecate shims prior to GA
#1956 commented on
Jun 18, 2025 • 0 new comments -
Zarf binaries on MacOS require code signing to avoid user difficulty
#458 commented on
Jun 18, 2025 • 0 new comments -
Zarf destroy panic
#2700 commented on
Jun 18, 2025 • 0 new comments -
alternative zarf config path as a CLI option
#2178 commented on
Jun 18, 2025 • 0 new comments -
Document a clear maintainership governance process
#2250 commented on
Jun 18, 2025 • 0 new comments -
Implement new variable attribute - required
#2225 commented on
Jun 18, 2025 • 0 new comments