~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/knotless

git that lives in your Atmosphere account

knotless.dev
1 collaborator

knotless 0.17.0 Latest 2 packages, 1 image

1
10

Release 0.17.0

Merged
Merged chadtmiller.com asked to merge into main from chadtmiller.com/knotless:release/next

Releases knotless 0.17.0, from the 4 change files on main: its changelog is below. Queue this pull to release it; once it lands, release.yml publishes the version and tags it. release-pull.yml keeps it up to date as change files land.

release-pull.yml

What changes

knotless 0.17.0, as knope release --override-version 0.17.0 makes it from main at f15972d0ee6e: the workspace version from 0.16.0 to 0.17.0 in Cargo.toml and the crates' Cargo.lock entries, the version's CHANGELOG.md section, and the change files removed.

Features

A repository's packages can be published and installed with npm

knotless-serve answers npm's registry protocol for each repository, so with @scope:registry=https://knotless.dev/npm/<did>/<repo key>/ in .npmrc, npm login (your handle and an app password), npm publish, npm install, npm view and npm search work, and npm deprecate yanks a version.

Fixes

A gist's link shows its code

A gist shared in a post or a chat now unfurls into a card of its own: the owner and the gist's first file, its description, the first lines of that file, highlighted, and how many files, comments and stars it has. Before, it showed the card of a repository, named by its TID, with open issues and pulls.

A gist file's box rings whole while you write in it

Writing a gist's file in the browser rings its whole box, name and text, as any field rings, rather than a line along its top.

The releases page shows how to install an npm package

A release published with npm publish shows the .npmrc line naming its repository's registry and the npm install that installs it, or for an unscoped package, the npm install of its tarball, rather than its .tgz.

Why

Users get the client side of main's changes only from a release. A 0.x minor change bumps the minor here, where knope alone would bump the patch.

How it was checked

The build is left to CI. client.minimum is left as it is: raise it by hand if a release in between harms repositories.

Approved

This is a mechanical release of 0.16.1. It bumps the workspace version in Cargo.toml and the Cargo.lock entries for all six workspace crates, which match the six members. It adds the 0.16.1 CHANGELOG section, and its text matches the two change files, which it deletes. I found nothing to change.

Approved

This is a mechanical release of 0.17.0. It bumps the workspace version in Cargo.toml and the six workspace crates' Cargo.lock entries. It adds the 0.17.0 CHANGELOG section, whose text matches the four change files, and it deletes those files. The minor bump is right because one change file is minor. The one npm feature goes under Features, and the three patch files go under Fixes. I found nothing to change.

I read the whole pull diff. I did not read the repo_diff from the approved commit to the head, which was too large to read: it also carries the base's changes, and those are not the pull's.

Merged as a98a628