Skip to content

v1.0.2 — ptc init: no token, action-based snippets

Latest
Latest

Choose a tag to compare

View all tags
@pavel-te pavel-te released this 24 Jul 05:57
v1.0.2
013883c

ptc init improvements, part of the CI on-ramp epic (ci18-7249). The translate pipeline is unchanged from v1.0.1.

ptc init no longer requires a token (ci18-7276)

detect_config is anonymous, and generating a config is the step you run before you have a token — so demanding one blocked the exact first-use path. With the API-token paywall in place, a trial org that cannot mint a token can still run ptc init and get a working .ptc-config.yml. When no token is set, no Authorization header is sent at all.

ptc init prints the ptc-action recipe (ci18-7254)

The old snippets curled the CLI from a floating v1.0.0 tag with no checksum, used actions/checkout@v4, and the GitLab job had no image and no bash — it would not start on a default Alpine runner. All three are gone. Both snippets now run through ptc-action:

- uses: actions/checkout@v7
- uses: OnTheGoSystems/ptc-action@v1
  with: { api-token: ..., config-file: .ptc-config.yml, create-pr: true }

The action SHA-pins the CLI and its dependencies, ships the right image, and is loop-safe. It is the same recipe the in-product token screen prints, so the CLI, the product and the action README no longer drift.

The CLI stays self-contained — ptc init ends by spelling out ./ptc-cli.sh --config-file .ptc-config.yml for anyone who does not want the action.

v1 now points here; v1.0.1 and v1.0.0 are unchanged if you pin them. 171 examples, 0 failures.

Assets 2
Loading