Skip to content

Add a release upload action - #66

Merged
nathansobo merged 15 commits into
masterfrom
upload-release
May 18, 2021
Merged

Add a release upload action#66
nathansobo merged 15 commits into
masterfrom
upload-release

Conversation

@nathansobo

Copy link
Copy Markdown
Contributor

The goal of this PR is to automatically upload Zed.dmg to a GitHub release whenever a tag starting with v is pushed.

@nathansobo nathansobo changed the title WIP: Add a release upload action Add a release upload action May 18, 2021
@nathansobo
nathansobo merged commit f7b37cd into master May 18, 2021
@nathansobo
nathansobo deleted the upload-release branch May 18, 2021 05:04
ShalashaskaOcelot pushed a commit to ShalashaskaOcelot/zed that referenced this pull request Aug 7, 2026
Bug zed-industries#66. The control's disabled gate asked has_outputs — literally "are there
output entries" — while the action it triggers runs clear_execution_record,
which also clears execution counts, run durations, last-executed timestamps and
the status markers. So after running cells that print nothing the notebook still
showed [3] ✓ 57ms everywhere while the button sat disabled.

CodeCell::has_execution_record now mirrors exactly what clear_execution_record
clears, and the notebook's gate uses it.

Also records the follow-mode design the user described (page-wise viewport
moves, selection carrying the progress signal) against the existing alternative-
follow-modes backlog item, with the open questions that need answering before
anyone implements it; and settles the line-numbers keybindings on Jupyter's
l / shift-l, both of which are free in the notebook's command-mode context.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JkvYRuX9r6PmLXpxNie2R7
jolutz pushed a commit to jolutz/zed that referenced this pull request Aug 8, 2026
ShalashaskaOcelot pushed a commit to ShalashaskaOcelot/zed that referenced this pull request Aug 13, 2026
Test results from 2026-08-11. Bugs zed-industries#7, zed-industries#66, zed-industries#67, zed-industries#68, zed-industries#70 and zed-industries#72 confirmed
fixed and removed; zed-industries#64 failed and stays open with the finding recorded; zed-industries#73's
repro is confirmed on Windows. Three fixes here.

zed-industries#69 (column titles wrapping their last character) was NOT fixed by the previous
attempt, and that attempt was aimed at the wrong layer. Measuring headers
semibold was a real discrepancy and stays, but the cause is that the table
renders at a different font SIZE from the one it measures with: ui's
font_buffer sets only the font family, so the size stayed ambient while
TableView::new measured against buffer_font_size. Every glyph then rendered a
fraction wider than measured, and the error accumulates with string length —
invisible on a 15-character title, just past the padding slack on a
16-character one, which is exactly the reported Column_number_9-fits,
Column_number_10-wraps threshold. The rendered size is now pinned to the
measured one.

zed-industries#74: a notebook whose file was deleted while Zed was closed didn't restore at
all, taking any unsaved changes with it. Nothing to do with deletion handling —
open_buffer deliberately returns an empty buffer for a path with no entry, so
the notebook parses, but try_open then demanded a worktree entry id and a
deleted file has none. That id was already optional on NotebookItem (it is only
a fallback for entry_id, which re-resolves from the path), so nothing needed it
to be present.

zed-industries#75: a restored untitled notebook showed no dirty marker until the next
keystroke. Same trap phase 69 fixed for file-backed notebooks and missed here:
rebuilding a notebook from stored JSON makes those cells their own baseline, so
it reads as clean. Contents are only stored when there ARE unsaved changes, so a
restored untitled notebook is unsaved by definition and now says so.

Also filed zed-industries#76: restoring unsaved changes over a file edited elsewhere gives no
notification. The conflict flag may well be set correctly and simply invisible
until save time, which is the first thing to check — the two possible causes
need different fixes, so nothing is attempted yet.

Backlogged from zed-industries#72's confirmation: a restart should read Restarting → Idle,
not Restarting → Starting → Idle.

Verified: clippy clean, 57 repl tests pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JkvYRuX9r6PmLXpxNie2R7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant