Pewarta Proxy

📋 Server Request & Proxy Logs

Loading active proxy settings...
Developed by Khairul Adha (adhexa.id)
Mengambil log server...

⚙️ Pengaturan Proxy Target

Skip to content

Tags: Zipstack/unstract-cli

Tags

v0.1.1

Toggle v0.1.1's commit message
chore: bump version to 0.1.1 [skip ci]

v0.1.0

Toggle v0.1.0's commit message
chore: bump version to 0.1.0 [skip ci]

v0.1.0rc1

Toggle v0.1.0rc1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
[MISC] Drop the `none` bump and clean up after a failed publish (#9)

* ci: drop the `none` bump and start the committed version at 0.0.0

`none` existed so the first release could publish the 0.1.0 already in the
file. With nothing published yet the file can start at 0.0.0 instead, and the
first release is an ordinary `minor` bump. After that `none` has no use: the
tag guard refuses a version already released, and so does PyPI.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ

* ci: keep the committed version at 0.1.0

The first release is being published from the version already in the file,
so it stays; only the `none` option goes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ

* ci: leave nothing behind when the publish fails

A publish that failed left the tag and the draft release in place, and for a
stable release the bump commit already on main; the next dispatch then
stopped on the tag guard until all three were removed by hand.

The bump commit now reaches main only after the publish, carried until then
by the tag alone, and a step that runs on failure removes the tag and the
draft release. It sits directly after the publish so a failure later in the
run, with the version already on PyPI, cannot remove the tag that names it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ

* ci: keep the tag when a failed publish still put the version on PyPI

The wheel and the sdist upload one after the other, so a publish can fail
with the version already served. The cleanup now asks PyPI first and leaves
the tag and draft release in place when it is.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ

* chore: start the committed version at 0.0.0

With nothing published, the first release is an ordinary `minor` bump rather
than a special case.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>