Skip to content

chore(main): release 0.13.0 - #44

Merged
Paullo9 merged 2 commits into
mainfrom
release-please--branches--main--components--SpectroKit
Nov 1, 2026
Merged

Paullo9 merged 2 commits into
mainfrom
release-please--branches--main--components--SpectroKit

Conversation

@macem-release

@macem-release macem-release Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.13.0 (2026-11-01)

⚠ BREAKING CHANGES

  • PooledQuantifier.run fits sum peaks by default when the data support them, so nets, at% and wt% change on spectra with pile-up. Migration: pass a policy with fit.sumPeaks = .off (or FitPolicy.exspyEquivalent), or sumEscape: SumEscapeModel(), to keep the old numbers. A stored QuantificationPolicy without the new field decodes as .off and its footer names the non-default policy.
  • PooledQuantifier.run fits sum peaks by default when the data support them, so nets, at% and wt% change on spectra with pile-up. Migration: pass a policy with fit.sumPeaks = .off (or FitPolicy.exspyEquivalent), or sumEscape: SumEscapeModel(), to keep the old numbers. A stored QuantificationPolicy without the new field decodes as .off and its footer names the non-default policy.
  • PooledQuantifier.run fits sum peaks by default when the data support them, so nets, at% and wt% change on spectra with pile-up. Migration: pass a policy with fit.sumPeaks = .off (or FitPolicy.exspyEquivalent), or sumEscape: SumEscapeModel(), to keep the old numbers. A stored QuantificationPolicy without the new field decodes as .off and its footer names the non-default policy.
  • PooledQuantifier.run fits sum peaks by default when the data support them, so nets, at% and wt% change on spectra with pile-up. Migration: pass a policy with fit.sumPeaks = .off (or FitPolicy.exspyEquivalent), or sumEscape: SumEscapeModel(), to keep the old numbers. A stored QuantificationPolicy without the new field decodes as .off and its footer names the non-default policy.
  • PooledQuantifier.run fits sum peaks by default when the data support them, so nets, at% and wt% change on spectra with pile-up. Migration: pass a policy with fit.sumPeaks = .off (or FitPolicy.exspyEquivalent), or sumEscape: SumEscapeModel(), to keep the old numbers. A stored QuantificationPolicy without the new field decodes as .off and its footer names the non-default policy.
  • SpectrumImageMetadata.sameScanAs4DCube (deprecated since 0.8.0) is removed: use sameScanAsCube. SpectroscopyExport.elementsLine(_:) is removed: use q.rows.map(.element).joined(separator: ", "). SpectroEELS no longer ships the 16 per-table GOS JSON files (about 6.8 MB): every edge reads the float32 pack, bit-identical tables, no number changes; CoreLossEdge.bundled is empty if the pack cannot be read.
  • pinned images and Xcode, --parallel, Pages permissions per job; drops iOS (#34)
  • Package.swift no longer declares iOS; it never built there.

Features

  • 0.13.0 removals (duplicate GOS JSON, sameScanAs4DCube, elementsLine, the extra Spectroscopy/ level) (#30) (aaea561)
  • broaden the continuum step at absorption edges by the detector by default (#65) (1a72013)
  • detector Si dead-layer step in the EDX simulator and a planted pool (#49) (df9082d)
  • downward confirmation rule (opt-in) and the uncorroborated tier (#46) (258c881)
  • downward confirmation rule (opt-in) and the uncorroborated tier in ProposalResult (258c881)
  • opt-in detector-broadened continuum step at absorption edges (#64) (93931fc)
  • opt-in NIST EPQ line-weight table for the quantification fit (#67) (4e9189b)
  • optional detector Si dead-layer term in the EDX continuum (#50) (6f9d132)
  • self-pair half bound on sum-peak questions and the opt-in overlap check (#54) (6a1b0c8)
  • take-off angle term in the sigma on wt% and at%, and per-pixel sigma maps (#55) (ff67d39)
  • the pooled fit models sum peaks when the strongest line's self pair is significant (#59) (e91a75a)
  • the proposer refines the energy axis on its own K picks (#47) (e650263)
  • the proposer refines the energy axis on its own K picks (two-line guard) (e650263)
  • thickness and dose terms in the sigma on wt% and at% (#53) (e0d9fed)
  • UnlistedLineCheck's Candidate, Move and initialiser are public (#42) (c3d2d93)

Bug Fixes

  • fitted dead-layer note follows the applied sum-peak model; refits repeat the reported dead layer (#68) (6ea2fb4)
  • kit texts name the method without a validation tag (#77) (ff6da75)
  • velox-tiny golden carries FormatoKit 0.12.0 acquisition fields (#71) (383d590)

Continuous Integration

  • pinned images and Xcode, --parallel, Pages permissions on the deploy job, no iOS claim (#17) (ec848d6)
  • pinned images and Xcode, --parallel, Pages permissions per job; drops iOS (#34) (ec848d6)

This PR was generated with Release Please. See documentation.

@macem-release
macem-release Bot force-pushed the release-please--branches--main--components--SpectroKit branch 14 times, most recently from 90cd4e5 to 3377079 Compare November 1, 2026 15:04
@macem-release
macem-release Bot force-pushed the release-please--branches--main--components--SpectroKit branch from 3377079 to e50034c Compare November 1, 2026 15:49
Keeps one copy of the #59 sum-peak migration note (it appeared five times) and adds #65's breaking change: the broadened continuum step is the new default, and FitPolicy.continuumEdgeStep = .sharp keeps the old numbers. Collapses the duplicate #46, #47 and CI lines. Notes under #68 that refits on the opt-in fitted dead layer repeat the reported thickness, so their numbers can change. The version is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Paullo9
Paullo9 merged commit 7117e70 into main Nov 1, 2026
13 checks passed
@Paullo9
Paullo9 deleted the release-please--branches--main--components--SpectroKit branch November 1, 2026 17:24
@macem-release

macem-release Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant