Skip to content

ci: Revalidate zed.dev after release - #59422

Merged
gaauwe merged 1 commit into
mainfrom
revalidate-after-release
Jun 16, 2026
Merged

ci: Revalidate zed.dev after release#59422
gaauwe merged 1 commit into
mainfrom
revalidate-after-release

Conversation

@gaauwe

@gaauwe gaauwe commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Updates CI to use the revalidate mechanism for updating zed.dev post release, instead of doing a full re-deploy.

Release Notes:

  • N/A

@cla-bot cla-bot Bot added the cla-signed The user has signed the Contributor License Agreement label Jun 16, 2026
@zed-community-bot zed-community-bot Bot added the staff Pull requests authored by a current member of Zed staff label Jun 16, 2026
@NeelChotai

Copy link
Copy Markdown
Member

🔪

@gaauwe
gaauwe added this pull request to the merge queue Jun 16, 2026
Merged via the queue into main with commit a851320 Jun 16, 2026
43 checks passed
@gaauwe
gaauwe deleted the revalidate-after-release branch June 16, 2026 15:02
This was referenced Jun 18, 2026
jolutz pushed a commit to jolutz/zed that referenced this pull request Aug 8, 2026
Updates CI to use the revalidate mechanism for updating zed.dev post
release, instead of doing a full re-deploy.

Release Notes:

- N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The user has signed the Contributor License Agreement staff Pull requests authored by a current member of Zed staff

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants