-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Comparing changes
Open a pull request
base repository: coder/coder
base: v2.33.8
head repository: coder/coder
compare: v2.33.9
- 6 commits
- 38 files changed
- 8 contributors
Commits on Jun 17, 2026
-
fix(coderd/httpmw): honor fixed lifetime for CLI API tokens (#26376) (#…
…26383) Backport of #26376 Original PR: #26376 — fix(coderd/httpmw): honor fixed lifetime for CLI API tokens Merge commit: 450ddff Requested by: @jdomeracki-coder Co-authored-by: Jakub Domeracki <jakub@coder.com>
Configuration menu - View commit details
-
Copy full SHA for e330564 - Browse repository at this point
Copy the full SHA e330564View commit details -
chore(provisioner/terraform): preserve existing AWS_SDK_UA_APP_ID (#2…
Configuration menu - View commit details
-
Copy full SHA for 41ab770 - Browse repository at this point
Copy the full SHA 41ab770View commit details -
fix(scripts/check_emdash.sh): skip emdash check when no diff base is …
…available (#26491) Backport of #26489 to `release/2.33`. ## Problem `scripts/check_emdash.sh` only resolves a base ref for pull requests (`GITHUB_BASE_REF`) or when `origin/main` is present. The `lint` job checks out with `fetch-depth: 1`, so on a release-branch push neither is available, and the script falls back to scanning **every tracked file**, flagging pre-existing emdash/endash characters the build did not introduce. This is the same failure mode seen on the `release/2.34` push build (run [27704528068](https://github.com/coder/coder/actions/runs/27704528068/job/81949529546)); `release/2.33` carries the same script and the same bug. ## Fix When no base ref can be determined (outside a pull request), skip the check instead of scanning the whole tree. `--all` still forces a full scan. Note: this branch carries an older variant of the script than `main`, so the change is applied by hand rather than cherry-picked, but the behavior matches #26489. ## Testing - Isolated no-base-ref repo (no `GITHUB_BASE_REF`, no `origin/main`): old script scans all files and fails on a pre-existing emdash; patched script skips and exits 0. - `shellcheck`, `shfmt`, `bash -n` clean. --- Generated by Coder Agents on behalf of @f0ssel.
Configuration menu - View commit details
-
Copy full SHA for 2e43114 - Browse repository at this point
Copy the full SHA 2e43114View commit details -
feat: implement package and cli tool for repairing oidc links (#26418) (
#26482) Backport of #26418 Original PR: #26418 — feat: implement package and cli tool for repairing oidc links Merge commit: 1d03e63 Requested by: @f0ssel > [!WARNING] > The automatic cherry-pick had conflicts. > Please resolve manually by cherry-picking the original merge commit: > > ``` > git fetch origin backport/26418-to-2.33 > git checkout backport/26418-to-2.33 > git reset --hard origin/release/2.33 > git cherry-pick -x -m1 1d03e63 > # resolve conflicts, then push > ``` --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Garrett Delfosse <garrett@coder.com> Co-authored-by: Steven Masley <Emyrk@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for d18ee68 - Browse repository at this point
Copy the full SHA d18ee68View commit details -
feat: deployment flag to auto handle changed oidc providers (#26419) (#…
…26484) Backport of #26419 Original PR: #26419 — feat: deployment flag to auto handle changed oidc providers Merge commit: 0e45ded Requested by: @f0ssel > [!WARNING] > The automatic cherry-pick had conflicts. > Please resolve manually by cherry-picking the original merge commit: > > ``` > git fetch origin backport/26419-to-2.33 > git checkout backport/26419-to-2.33 > git reset --hard origin/release/2.33 > git cherry-pick -x -m1 0e45ded > # resolve conflicts, then push > ``` --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Garrett Delfosse <garrett@coder.com> Co-authored-by: Steven Masley <Emyrk@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 08cf114 - Browse repository at this point
Copy the full SHA 08cf114View commit details -
Configuration menu - View commit details
-
Copy full SHA for 355536e - Browse repository at this point
Copy the full SHA 355536eView 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 v2.33.8...v2.33.9