Repository navigation
Comparing changes
Open a pull request
base repository: canonical/chisel
base: v1.4.1
head repository: canonical/chisel
compare: v1.4.2
- 11 commits
- 19 files changed
- 5 contributors
Commits on Apr 20, 2026
-
fix(ci): replace GITHUB_TOKEN by fine-grained one (#284)
After the recent changes to the `GITHUB_TOKEN`, the `build.yml` workflow can no longer push the release artifacts to the GitHub release: https://github.com/canonical/chisel/actions/runs/24026969346 This PR replaces the `GITHUB_TOKEN` with a new one, managed by us. This new token has `contents: write` permissions (similarly to the `GITHUB_TOKEN`), which are unfortunately broad, because GitHub does not offer fine-grained control for releases. The use of the secret is bound to a single step, which runs our own CI script, and always in the context of the base repo and on `release` events.
Configuration menu - View commit details
-
Copy full SHA for c85fc8a - Browse repository at this point
Copy the full SHA c85fc8aView commit details
Commits on Apr 27, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 058417e - Browse repository at this point
Copy the full SHA 058417eView commit details -
ci: set specific name on arch-specific scan results (#285)
Avoid collisions between scan results for the different arch-specific artifacts. Also set the needed permissions on the GITHUB_TOKEN to upload the security report. A fine-grained token cannot be used as this specific action only accept the GITHUB_TOKEN.
Configuration menu - View commit details
-
Copy full SHA for b25a781 - Browse repository at this point
Copy the full SHA b25a781View commit details -
fix: GlobDistance handles / and * correctly (#281)
Fixes the long-standing bug in #63.
Configuration menu - View commit details
-
Copy full SHA for 9310192 - Browse repository at this point
Copy the full SHA 9310192View commit details
Commits on Jun 1, 2026
-
chore: rename errors to comply with ST1012 (#293)
Rename two errors and remove the associated linter exclusions to comply with ST1012.
Configuration menu - View commit details
-
Copy full SHA for efdbb5d - Browse repository at this point
Copy the full SHA efdbb5dView commit details -
fix: unicode is handled properly in strdist (#280)
This PR fixes a common bug when handling strings in Go. The for loop: for bi, br := range b { ... lst[bi+1] = cost } Is iterating over a string and using bi which is the byte offset to store things in lst instead of the current rune count. In the case where the characters are ASCII it works because each rune is 1 byte but in the case of runes that take more than 1 byte this fails (see the added test case).Configuration menu - View commit details
-
Copy full SHA for ebec450 - Browse repository at this point
Copy the full SHA ebec450View commit details
Commits on Jun 15, 2026
-
build(workshop): add initial workshop configuration (#297)
Add workshop configuration, with agent SDKs to enable standard agent-based work.
Configuration menu - View commit details
-
Copy full SHA for d9040ff - Browse repository at this point
Copy the full SHA d9040ffView commit details
Commits on Jun 16, 2026
-
feat: support SHA384 for cache entries (#298)
Some package stores only publish SHA3-384 hashes. This PR enables storing entries in the cache using SHA3-384 hashes. Consumers of the cache package must now explicitly select the algorithm to be used to create/write/read an entry.
Configuration menu - View commit details
-
Copy full SHA for 23fc7e4 - Browse repository at this point
Copy the full SHA 23fc7e4View commit details
Commits on Jul 6, 2026
-
Configuration menu - View commit details
-
Copy full SHA for eb3a622 - Browse repository at this point
Copy the full SHA eb3a622View commit details -
Configuration menu - View commit details
-
Copy full SHA for ea61b84 - Browse repository at this point
Copy the full SHA ea61b84View commit details
Commits on Jul 7, 2026
-
fix: prevent digest-mismatch on archive updates (#296)
Chisel intermittently fails with `expected digest X, got Y` when Ubuntu's archive is mid-publication and InRelease is temporarily inconsistent with `Packages.gz` at the named path (a window we observed lasting at least 39 minutes against the same publication in real CI runs for [Ella Core](https://github.com/ellanetworks/core)). Fetch the package index by content hash using apt's `Acquire-By-Hash` , which Ubuntu archives have advertised since 16.04 (2016), so the URL itself encodes the expected bytes; falls back to the named path when an archive doesn't advertise the feature or a specific hash has been garbage-collected. Fixes #295 Reference: https://wiki.debian.org/DebianRepository/Format#Acquire-By-Hash
Configuration menu - View commit details
-
Copy full SHA for 1262471 - Browse repository at this point
Copy the full SHA 1262471View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.4.1...v1.4.2