Skip to content

release: v0.4.0 #42

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
marcohost33-maker merged 1 commit into from
Jun 7, 2026
Merged

release: v0.4.0 #42

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
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,13 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

## [0.4.0] — 2026-06-07

Release cut: everything below shipped on `main` between `v0.3.0` (2026-05-28)
and this tag (18 commits, PRs #34–#41 — audit waves 2026-06-04/06-06 + D14
Comment on lines +11 to +12

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 7, 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 Correct the release-cut commit and PR scope

The new release section says everything below came from 18 commits and PRs #34–#41, but the section also documents changes introduced by earlier PRs such as #28, #31, #32, and #33, while the repository history from the v0.3.0 version-sync commit through the pre-release parent contains only 15 commits. Since this statement is presented as the release audit trail, it gives readers an incorrect scope and should be replaced with the actual commit/PR range.

Useful? React with 👍 / 👎.

physics-scaling). MINOR bump per SemVer: backward-compatible API additions
(`gap=` forwarding, `TransientGridWarning`, `SOURCE_DATE_EPOCH`).

### Fixed
- D14 transient time-grid physics-scaling (audit 2026-06-06, P2-1):
`diagnostics.transient.trans_amplitude_ratio` (`sup_t ||e^{tL}||_2`)
Expand Down
4 changes: 2 additions & 2 deletions CITATION.cff
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@ message: "If you use this software, please cite it as below."
type: software
authors:
- name: "Coworker Research"
version: "0.2.0"
date-released: "2026-04-17"
version: "0.4.0"

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 7, 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 Update the preferred citation for v0.4.0

When citation consumers honor preferred-citation—including the GitHub citation widget referenced in README.md—they will still present the software as v0.2.0 because its title remains unchanged at line 31, even though this release now declares version: "0.4.0". This gives users incorrect version provenance for the new release; update the preferred-citation title or remove its embedded version.

Useful? React with 👍 / 👎.

date-released: "2026-06-07"
license: Apache-2.0
repository-code: "https://github.com/marcohost33-maker/Liouscope"
url: "https://github.com/marcohost33-maker/Liouscope"
Expand Down
2 changes: 1 addition & 1 deletion src/liouscope/_version.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,4 @@
so setuptools can read it statically at build time.
"""

__version__ = "0.3.0"
__version__ = "0.4.0"
Loading