Lines Matching refs:changes
20 `main` is intended to give time to fuzz changes on `main` as well as allow
34 * Commit the changes
35 * Push these changes to a temporary `ci/*` branch
43 * All changes land on `main` first, then are backported to `release-X.Y.Z` as
60 of pushed changes for the special marker added by `release-process.yml`. If
79 * All changes must land on `main` first (if applicable) and then get backported
88 * Patch releases must not contain API-breaking changes in public crates. The
90 about in terms of breaking changes.
92 * Wasm-level ABI-breaking changes are by default not allowed in patch releases.
106 1. **Necessary changes are backported to the `release-2.0.0` branch from
113 semver-API-breaking changes (in the strictest sense). All security fixes
116 * Don't forget to write patch notes in `RELEASES.md` for backported changes.
121 * The changes will be committed with a special marker indicating a release
145 * (theoretically) All changes on `main` bundle an appropriate update of