Skip to content

Conversation

@sderev
Copy link
Owner

@sderev sderev commented Feb 3, 2026

What changed

  • Move demo GIFs to assets/images and update README.md image references.
  • Bump pyproject.toml to 0.1.0, refresh uv.lock, and collect/reconcile changelog entries into CHANGELOG.md.
  • Switch release publishing to uv publish with PyPI trusted publishing in .github/workflows/release.yml.
  • Keep prerelease skip and add stable tag guard so only vX.Y.Z / X.Y.Z tags publish.
  • Fix fail-open scriv print handling in .github/workflows/lint.yml.
  • Improve CLI helper UX messages in wslshot/cli.py (conflict wording, symlink hint, auto-stage warning) and update tests.
  • Add a concise AI agent snippet section to README.md and align docs with actual CLI behavior (--no-transfer conflicts, output style behavior, destination caveat in git repos, supported source formats).

Why

  • Make 0.1.0 release artifacts, changelog, docs, and publish automation consistent and ready.
  • Reduce user confusion in CLI/runtime messaging and README guidance.

How to test

  • Run gate.
  • Run uv build and verify wheel/sdist are created in dist/.
  • Run uv publish --dry-run --trusted-publishing never --check-url https://pypi.org/simple --username __token__ --password dummy.
  • Manual CLI checks:
  • Run uv run wslshot --no-transfer --destination /tmp and verify the explicit conflict message for --destination + --no-transfer.
  • Create a symlinked config path and run uv run wslshot --no-transfer; verify the symlink hint is generic and actionable.
  • Trigger auto-stage failure scenario and verify warning is concise + follow-up hint is present.
  • Manual docs checks:
  • Open README.md and verify demo GIF links resolve from assets/images/.
  • Verify AI agent snippet and “Look at my last screenshot.” example read clearly and match command behavior.

Risk/comp notes

  • Moderate: release workflow/auth path changed to trusted publishing; compatibility depends on matching PyPI trusted publisher config.
  • Low runtime risk: CLI behavior is unchanged; message wording is clarified.

Changelog fragment: yes (collected into CHANGELOG.md for 0.1.0).

sderev and others added 2 commits February 3, 2026 01:00
Summary:

* Relocate `demo.gif` and `demo-vim.gif` into `assets/images`.

* Update README Quick Start and image references.

* Run legacy `plain_text` config test from the source directory.

Co-authored-by: AI <ai@sderev.com>
Summary:

* Update `pyproject.toml` to `0.1.0`.

* Collect `changelog.d` fragments into `CHANGELOG.md`.

* Remove collected fragments.

Co-authored-by: AI <ai@sderev.com>
@sderev sderev changed the title Prepare release Prepare 0.1.0 release Feb 3, 2026
Summary:

* Update `uv.lock` after rebase and `scriv collect`.

Co-authored-by: AI <ai@sderev.com>
@sderev sderev force-pushed the release-readiness branch 3 times, most recently from e01944e to 4cc1010 Compare February 5, 2026 21:23
@sderev
Copy link
Owner Author

sderev commented Feb 5, 2026

@codex review

sderev and others added 3 commits February 5, 2026 23:29
* Replace `gh-action-pypi-publish` with `uv publish --trusted-publishing always`.
* Keep prerelease skip and add stable tag guard (`vX.Y.Z` / `X.Y.Z`).

Co-authored-by: AI <ai@sderev.com>
* Avoid fail-open behavior in changelog fragment validation.
* Treat exit code `2` as "no fragments" and fail on other errors.

Co-authored-by: AI <ai@sderev.com>
* Replace ambiguous `--destination` + `--no-transfer` conflict text with explicit guidance.
* Make symlink security hint command-agnostic in shared config path handling.
* Simplify auto-staging failure warning text while keeping the actionable follow-up hint.
* Update `tests/test_no_transfer.py` for the new conflict wording.

Co-authored-by: AI <ai@sderev.com>
@chatgpt-codex-connector
Copy link

Codex Review: Didn't find any major issues. 🚀

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

* Add the AI agent snippet section with a user prompt example for screenshots.
* Clarify output style behavior, `--no-transfer` conflicts, destination behavior in git repos, and supported source formats.
* Fold the pending `--optimize` entry into `CHANGELOG.md` and remove collected fragment `changelog.d/20260205_213305_sderev.md`.

Co-authored-by: AI <ai@sderev.com>
@sderev sderev force-pushed the release-readiness branch from 4bfd9c1 to 0a62079 Compare February 5, 2026 22:35
@sderev sderev changed the title Prepare 0.1.0 release Prepare release readiness Feb 5, 2026
@sderev sderev changed the title Prepare release readiness Prepare 0.1.0 release readiness Feb 5, 2026
@sderev sderev merged commit 0a62079 into main Feb 5, 2026
6 checks passed
@sderev sderev deleted the release-readiness branch February 5, 2026 22:37
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