-
Notifications
You must be signed in to change notification settings - Fork 0
Prepare 0.1.0 release readiness
#20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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>
Summary: * Update `uv.lock` after rebase and `scriv collect`. Co-authored-by: AI <ai@sderev.com>
e01944e to
4cc1010
Compare
Owner
Author
|
@codex review |
* 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>
|
Codex Review: Didn't find any major issues. 🚀 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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>
4bfd9c1 to
0a62079
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed
assets/imagesand updateREADME.mdimage references.pyproject.tomlto0.1.0, refreshuv.lock, and collect/reconcile changelog entries intoCHANGELOG.md.uv publishwith PyPI trusted publishing in.github/workflows/release.yml.vX.Y.Z/X.Y.Ztags publish.scriv printhandling in.github/workflows/lint.yml.wslshot/cli.py(conflict wording, symlink hint, auto-stage warning) and update tests.README.mdand align docs with actual CLI behavior (--no-transferconflicts, output style behavior, destination caveat in git repos, supported source formats).Why
0.1.0release artifacts, changelog, docs, and publish automation consistent and ready.How to test
gate.uv buildand verify wheel/sdist are created indist/.uv publish --dry-run --trusted-publishing never --check-url https://pypi.org/simple --username __token__ --password dummy.uv run wslshot --no-transfer --destination /tmpand verify the explicit conflict message for--destination+--no-transfer.uv run wslshot --no-transfer; verify the symlink hint is generic and actionable.README.mdand verify demo GIF links resolve fromassets/images/.Risk/comp notes
Changelog fragment: yes (collected into
CHANGELOG.mdfor0.1.0).