Skip to content

Release v0.1.20 #274

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.

Sign up for GitHub

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
Sythos merged 1 commit into from
Oct 8, 2026
Merged

Release v0.1.20 #274

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion crates/cordiale-core/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "cordiale-core"
version = "0.1.19"
version = "0.1.20"
edition = "2021"
license = "MIT"
publish = false
Expand Down
2 changes: 1 addition & 1 deletion crates/cordiale-ui/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "cordiale-ui"
version = "0.1.19"
version = "0.1.20"
edition = "2021"
license = "MIT"
publish = false
Expand Down
14 changes: 14 additions & 0 deletions docs/release-notes/v0.1.20.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
Cordiale package version: `${PACKAGE_VERSION}` (tag version `${VERSION}`, GitHub Actions run ID `${RUN_ID}`, attempt `${RUN_ATTEMPT}`).

@chatgpt-codex-connector chatgpt-codex-connector Bot Oct 8, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Replace unsupported release-note placeholders

When a v0.1.20 tag triggers the Packages workflow, .github/workflows/packages.yml lines 515–526 substitutes ${BUILD_ID} and ${BUILD_ATTEMPT}, not the ${RUN_ID} and ${RUN_ATTEMPT} used here. Consequently, the published GitHub release body will display those two placeholders literally; use the placeholder names supported by the renderer or extend the renderer to replace them.

Useful? React with 👍 / 👎.


Where four numeric components are supported, the fourth is the GitHub Actions run ID. Windows VERSIONINFO stores its reduction below 65535 in the numeric component and preserves the full ID in string metadata. macOS keeps the tag in `CFBundleShortVersionString`, uses a valid compact `CFBundleVersion`, and records the full run ID in `CordialeBuildID` and `CordialeBuildVersion`.

Tester note: Cordiale handles all currently inventoried Grappa event kinds. Only message events are rendered as chat lines; see the README for behavior and current limitations.

Heads up: every package here is unsigned, on every platform — no code-signing cert anywhere, even though the filenames don't say so. Windows SmartScreen and some Linux package managers might complain about it; that's expected for an unsigned, community-built app, not a sign of tampering. Each artifact still ships a SHA256SUMS file and a build provenance attestation if you want to verify it yourself — see [docs/installation.md](https://github.com/Sythos/Cordiale/blob/main/docs/installation.md).

## Highlights
A small but careful release, mostly about admin tools that now say "are you sure?" and "here's what went wrong" instead of shrugging.

* **Network delete thinks twice.** In the admin area, deleting a network is blocked until the scrollback count is known. If Cordiale doesn't know how much history is at stake, it won't let you press the big red button. Look before you leap.
* **Visitor delete failures get a voice.** When deleting a visitor fails, you now see the error instead of a silent refresh that left you wondering whether anything happened. Bad news, but at least it's honest news.
* **Ban type stays in sync.** The default ban type now follows Grappa's ban-mask-form setting, so your bans start out the way the server expects. One less dropdown to second-guess.
Loading