Release prep: batched version bumps for 27 packages#1262
Merged
Conversation
Bumps every package with unreleased changes since its last registered version. All changes reviewed as SAFE (docs/CI/QA scaffolding, docstrings, mechanical import/refactor cleanups, or confirmed non-breaking bug fixes) - no new public API surface, so all bumps are patch-level. No internal compat floors required raising: every sibling's existing floor on a bumped package already permits the new patch version, and none of the bumped packages expose new symbols that any sibling's source depends on. Packages released: - Optimization 5.6.4 -> 5.6.5 (docs, CI, test scaffolding only; no src changes) - OptimizationAuglag 2.0.1 -> 2.0.2 (docstrings; Reexport/Random compat) - OptimizationBBO 0.4.8 -> 0.4.9 (mechanical BBO_* struct-gen refactor + docstrings) - OptimizationBase 5.2.0 -> 5.2.1 (docstrings; internal non-exported eltype-promotion fix) - OptimizationCMAEvolutionStrategy 0.3.9 -> 0.3.10 (docstring only) - OptimizationEvolutionary 0.4.10 -> 0.4.11 (bug fix: drop bad initial-point arg breaking multi-objective exploration) - OptimizationGCMAES 0.3.9 -> 0.3.10 (docstring; mechanical closure-definition cleanup) - OptimizationIpopt 1.2.2 -> 1.2.3 (compat-only: QA/test deps) - OptimizationLBFGSB 1.4.2 -> 1.4.3 (bug fix: define `res` fallback so 0-iteration solves don't UndefVarError) - OptimizationMOI 1.3.2 -> 1.3.3 (mechanical: drop dead import list) - OptimizationMadNLP 2.2.1 -> 2.2.2 (docstring; compat-only otherwise) - OptimizationManopt 1.3.3 -> 1.3.4 (bug fix: maxtime now converted to a Period for Manopt.StopAfter; explicit imports; docstrings) - OptimizationMetaheuristics 0.3.7 -> 0.3.8 (bug fix: initialize opt_bounds so unbounded problems don't UndefVarError) - OptimizationMultistartOptimization 0.3.6 -> 0.3.7 (compat-only: QA/test deps) - OptimizationNLPModels 1.3.2 -> 1.3.3 (docstrings only) - OptimizationNLopt 0.3.12 -> 0.3.13 (mechanical: drop stale theta-memoization flagged by JET) - OptimizationNOMAD 0.3.7 -> 0.3.8 (mechanical: merge duplicated if/else branches; docstring) - OptimizationODE 0.1.7 -> 0.1.8 (docstrings only) - OptimizationOptimJL 0.4.15 -> 0.4.16 (compat-only: QA/test deps) - OptimizationOptimisers 0.3.18 -> 0.3.19 (bug fix: initialize `x` so 0-iteration solves don't UndefVarError) - OptimizationPRIMA 0.3.9 -> 0.3.10 (docstrings; defensive else-branch) - OptimizationPolyalgorithms 0.3.7 -> 0.3.8 (docstring only) - OptimizationPyCMA 1.3.2 -> 1.3.3 (docstring; move stray Test dep from [deps] to [extras]) - OptimizationSciPy 0.4.7 -> 0.4.8 (bug fix: pytypeof -> pytype, prior fallback path would error; docstrings) - OptimizationSophia 1.3.2 -> 1.3.3 (bug fix: initialize `x` so 0-iteration solves don't UndefVarError) - OptimizationSpeedMapping 0.2.6 -> 0.2.7 (bug fix: distinguish MaxIters/MaxTime retcodes instead of collapsing to Failure) - SimpleOptimization 1.2.2 -> 1.2.3 (bug fix: guard nothing before arithmetic in AD-backend-missing error path) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Batched patch-version bumps for every package in this monorepo (root + all
lib/*) whose default-branch tree currently differs from its last version registered in JuliaRegistries/General. This is a version-bump-only PR — no source, docs, or CI changes.Scope-check methodology
For each package, I diffed from the commit whose subdirectory tree hash matches the currently-registered
git-tree-sha1(per General'sVersions.toml) up to currentHEAD, scoped to that package's own subdirectory (or non-lib/paths for root). Every change was individually reviewed and classified as SAFE (docs/CI/QA scaffolding, docstrings, mechanical/behavior-preserving refactors, or confirmed non-breaking bug fixes) — nothing introduces new public API surface or a breaking signature change, so every bump is a patch release.Compat floor cascade
Checked every sibling package's
[compat]floor on each bumped package. No floor raises were needed: every existing floor (e.g.OptimizationBase = "5"/"5.1") already permits the corresponding new patch version, and none of the bumped packages expose new symbols that any sibling's source actually uses. Root's compat floors onOptimizationBase/OptimizationOptimJL/OptimizationOptimisersare likewise already permissive enough.Packages released
src/changesBBO_*struct-generation refactor (same generated structs) + docstrings_cons_out_eltype) for nested-dual AD correctnessresfallback so a 0-iteration solve doesn'tUndefVarErrormaxtimenow converted to aPeriodforManopt.StopAfter; explicit-import cleanup; docstringsopt_boundsso unbounded problems don'tUndefVarErrorxso a 0-iteration solve doesn'tUndefVarErrorelsebranch on a closed solver-type setTestdep from[deps]to[extras](was incorrectly a hard runtime dep)pytypeof→pytype(the former doesn't exist in PythonCall; the fallback path would have errored); docstringsxso a 0-iteration solve doesn'tUndefVarErrorMaxIters/MaxTimeretcodes instead of collapsing everything non-converged toFailurenothingbefore arithmetic in the AD-backend-missing error pathTest plan
lib/files) from its last-registered commit to HEAD and manually reviewed each change🤖 Generated with Claude Code