Skip to content

chore(release): v1.2.0 - #510

Merged
q-soriarty merged 653 commits into
mainfrom
release/v1.2.0
Nov 16, 2026
Merged

q-soriarty merged 653 commits into
mainfrom
release/v1.2.0

Conversation

@q-soriarty

@q-soriarty q-soriarty commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Release v1.2.0: develop into main (follows docs/releasing.md).

The CHANGELOG.md [1.2.0] section opens with Breaking changes, three changes that can break existing scripts:

The two ### Fixed sections of [Unreleased] are merged into one, and the stray blank lines inside the bullet lists are removed. The Changed entries of #167 and #177 are now marked Breaking:, like #429.

Also in this release: the manual on MkDocs Material with the Qubernetic brand theme (#501, #505).

After merge: tag v1.2.0 on main (admin), publish the draft release, back-merge main into develop.

Closes #509

feat(alias): add alias set, list, delete and import
feat(issue): add --web to issue view, list, create and comment
feat(pr): add --web to pr view, list, create, comment and diff
q-soriarty and others added 26 commits November 16, 2026 12:38
The link checks saw inline links only, so a reference definition such as
[x]: ../manual/copia-cli_gone.md passed go test and failed only the
strict site build. They now read reference definitions too.

escapeAngles knows only backtick fences and code spans within one line.
A new check classifies the lines of each generated page the way MkDocs
reads them and fails on "<" in a fenced or indented code block or in
a code span, also one a line break splits. Definition continuation lines,
which printFlags indents by four spaces, are prose, not code.

Refs #501
pkg/cmdutil defines the text of shared flags shown on the command pages
(--json, --jq, --template), and a cobra or pflag bump in go.mod and go.sum
can change the pages too. Add the three to push.paths of docs.yml and to
TestDocsPathsCoverTheGenerator.

Refs #501
The secret checks counted the literal "secrets.", so secrets['X'] or
toJSON(secrets) in another step slipped by; they now match the secrets
context as a word. TestDocsBuildIsStrict was a substring match that
passed with "|| true" or continue-on-error; the build step must now run
the one mkdocs command and neither the step nor the build job may set
continue-on-error. The concurrency group must be exactly
pages-${{ github.ref }}, not any group that contains github.ref.

Refs #501
pr create defaults the head to the current branch only with --web or
--fill; with --title alone it sends an empty head. Home and the quick
start now show copia-cli pr create --fill and say what --fill takes from
the commits, and Home links to the releases page.

Refs #501
curl does not expand *, so the latest/download URLs of the .deb and .rpm
returned 404. The package names hold the version (.goreleaser.yml sets
no nfpm file name template, so goreleaser's default
copia-cli_<version>_linux_<arch> applies), and no stable latest/download
name exists. The page now sends the reader to the latest release and
shows the install command with a <version> placeholder.

Refs #501
just docs-build and docs-serve resolved mkdocs-material==9.7.6 and its
dependencies freely, while CI installs the hashed set of
docs/site/requirements.txt. Both recipes now run
uv run --with-requirements requirements.txt from docs/site, so a local
strict build uses the versions CI uses.

Refs #501
The docs/site/brand submodule pointed at cf6e122 on the brand
repository's feature branch. That branch is now merged, so the pin moves
to the merge commit 7f030a6 on develop, the commit the brand remote will
serve to CI. The theme files are unchanged between the two commits.

Refs #501
Copia answers GET /repos/{owner}/{repo}/collaborators/{login}/permission
with a plain-text 404, so the list shows LOGIN and NAME only and --json
takes login and full_name. The integration test checks that the account
is listed after add -p read, without the permission-route probe.

Refs #486
…-list-add

feat(repo): add repo collaborator list and add
Check GET /repos/{owner}/{repo}/collaborators/{login} first, since Gitea
answers 204 to a delete of a non-collaborator, then DELETE it. --yes is
required and checked before anything else.

Closes #50
…remove

feat(repo): add repo collaborator remove
ci: bump every codeql-action step to 4.39.3
feat(repo): add the gpg-key and repo collaborator commands
…elop/peter-evans/create-pull-request-8.1.2

ci: bump peter-evans/create-pull-request from 8.1.1 to 8.1.2
…/github.com/itchyny/gojq-0.12.20

chore(deps): bump github.com/itchyny/gojq from 0.12.19 to 0.12.20
…/github.com/spf13/pflag-1.1.0

chore(deps): bump github.com/spf13/pflag from 1.0.10 to 1.1.0
# Conflicts:
#	CHANGELOG.md
#	CLAUDE.md
#	docs/site/_includes/sidebar.html
Fetch qubernetic/brand over HTTPS and set update = none, so
git clone --recursive and a bare git submodule update --init no longer
fail without access to the private theme. The site build fetches it
with git submodule update --init --checkout docs/site/brand.
The ubuntu-24.04 runner already has pip3, so the apt-get update only
made the deploy on main depend on the apt mirrors.
The extensionless Jekyll addresses redirect to the new pages, the .html
ones do not. Link the completion page with its trailing slash.
@codecov

codecov Bot commented Nov 16, 2026

Copy link
Copy Markdown

@q-soriarty
q-soriarty merged commit aef09fe into main Nov 16, 2026
8 checks passed
@q-soriarty
q-soriarty deleted the release/v1.2.0 branch November 16, 2026 18:45
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.

Release v1.2.0

2 participants