Skip to content

chore(deps): bump numpy from 2.0.2 to 2.5.2 in /skills/remove-ai-marks/scripts - #10

Merged
guillaumemeyer merged 1 commit into
mainfrom
dependabot/pip/skills/remove-ai-marks/scripts/numpy-2.5.2
Aug 13, 2026
Merged

guillaumemeyer merged 1 commit into
mainfrom
dependabot/pip/skills/remove-ai-marks/scripts/numpy-2.5.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 13, 2026

Copy link
Copy Markdown
Contributor

Bumps numpy from 2.0.2 to 2.5.2.

Release notes

Sourced from numpy's releases.

v2.5.2 (Aug 9, 2026)

NumPy 2.5.2 Release Notes

The NumPy 2.5.2 is a patch release that fixes bugs discovered after the 2.5.1 release. The big news is that it includes wheels for the newly released Python 3.15.0rc1.

This release supports Python versions 3.12-3.15

C API changes

PyArray_StringDTypeObject is opaque under the abi3t stable ABI

The PyArray_StringDTypeObject was accidentally exposed in NumPy 2.5 when targeting the free-threading-compatible stable ABI (Py_TARGET_ABI3T). PyArray_StringDTypeObject is now an opaque struct: extensions compiled that way cannot access its fields, since the struct layout depends on the size of the object header. Any code that accessed PyArray_StringDTypeObject fields in an abi3t build would have crashed, so we are making this API change in a bugfix release.

The NpyString allocator API remains usable by passing the descriptor object pointer, e.g. NpyString_acquire_allocator((PyArray_StringDTypeObject *)descr).

(gh-31771)

Contributors

A total of 16 people contributed to this release. People with a "+" by their names contributed a patch for the first time.

  • Abhijeetsingh Meena +
  • Charalampos Stratakis
  • Charles Harris
  • Chris Ninham +
  • David Woods
  • Geonho +
  • Gopu Yeshwanth Reddy +
  • Iason Krommydas
  • Ijtihed Kilani
  • Jelle Zijlstra +
  • Joren Hammudoglu
  • Kumar Aditya
  • Mike Boyle
  • Nathan Goldbaum
  • Raghuveer Devulapalli
  • Sebastian Berg

... (truncated)

Changelog

Sourced from numpy's changelog.

This is a walkthrough of the NumPy 2.4.0 release on Linux, which will be the first feature release using the numpy/numpy-release <https://github.com/numpy/numpy-release>__ repository.

The commands can be copied into the command line, but be sure to replace 2.4.0 with the correct version. This should be read together with the :ref:general release guide <prepare_release>.

Facility preparation

Before beginning to make a release, use the requirements/*_requirements.txt files to ensure that you have the needed software. Most software can be installed with pip, but some will require apt-get, dnf, or whatever your system uses for software. You will also need a GitHub personal access token (PAT) to push the documentation. There are a few ways to streamline things:

  • Git can be set up to use a keyring to store your GitHub personal access token. Search online for the details.

Prior to release

Add/drop Python versions

When adding or dropping Python versions, multiple config and CI files need to be edited in addition to changing the minimum version in pyproject.toml. Make these changes in an ordinary PR against main and backport if necessary. We currently release wheels for new Python versions after the first Python RC once manylinux and cibuildwheel support that new Python version.

Backport pull requests

Changes that have been marked for this release must be backported to the maintenance/2.4.x branch.

Update 2.4.0 milestones

Look at the issues/prs with 2.4.0 milestones and either push them off to a later version, or maybe remove the milestone. You may need to add a milestone.

Check the numpy-release repo

... (truncated)

Commits
  • 48fecee REL: Prepare for the NumPy 2.5.2 release (#32226)
  • ecf599c Merge pull request #32221 from charris/backport-32151
  • 3c7ac97 Merge pull request #32220 from charris/backport-32205
  • 23b30f4 BUG: avoid segfaults when legacy copyswap slot is not defined (#32151)
  • 4964ca8 TYP: isclose shape-typing fix for 2d array-likes (#32205)
  • c37ed94 MAINT: Skip limited_api tests on some platforms. (#32214)
  • 5cfd73b Merge pull request #32206 from charris/update-cibuildwheel
  • d8262bc MAINT: Update cibuildwheel to v4.2.0
  • 988d94d Merge pull request #32158 from charris/backport-32133
  • b2e4f97 BUG: avoid possible stack overflow in arraydescr_dealloc (#32133)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Aug 13, 2026
@dependabot
dependabot Bot requested a review from guillaumemeyer as a code owner August 13, 2026 04:17
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Aug 13, 2026
guillaumemeyer
guillaumemeyer previously approved these changes Aug 13, 2026

@guillaumemeyer guillaumemeyer left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Approved via API (dependabot bump review).

Bumps [numpy](https://github.com/numpy/numpy) from 2.0.2 to 2.5.2.
- [Release notes](https://github.com/numpy/numpy/releases)
- [Changelog](https://github.com/numpy/numpy/blob/main/doc/RELEASE_WALKTHROUGH.rst)
- [Commits](numpy/numpy@v2.0.2...v2.5.2)

---
updated-dependencies:
- dependency-name: numpy
  dependency-version: 2.5.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/pip/skills/remove-ai-marks/scripts/numpy-2.5.2 branch from 735f5b9 to 4829a79 Compare August 13, 2026 04:27
@guillaumemeyer
guillaumemeyer merged commit 9bfb639 into main Aug 13, 2026
3 checks passed
@dependabot
dependabot Bot deleted the dependabot/pip/skills/remove-ai-marks/scripts/numpy-2.5.2 branch August 13, 2026 04:30
guillaumemeyer added a commit that referenced this pull request Aug 31, 2026
A no-op row keeps before_pos (so it is still in the clear-rate denominator)
but has cleared=None, so it never counts as a clear. The help text said
'excluded from the clear-rate denominator', which was wrong; state that it
never counts as a clear.
guillaumemeyer added a commit that referenced this pull request Aug 31, 2026
* feat(bench): SynthID recipe search + robust measurement

Add a multi-objective recipe search to the SynthID-text benchmark that
answers "what combination of strategies, and at what intensity, best
clears the mark while preserving meaning and reading human?" while
hardening the measurements the search depends on.

rewrite_text.py:
- No-op guard: a rewrite that changed fewer than --noop-lex-floor (0.05)
  bigrams is flagged noop in --json-stats with a warning, so a near-verbatim
  output can no longer be read as 0% clear (the misleading backtranslate row).
- strength x intensity: --rewrite-level now modulates the named strength
  prompt instead of replacing it, so a (strength, intensity) step is
  expressible for recipe composition.

bench_synthid_text.py:
- Surface noop + robust_cleared per row, aggregate noop_n / robust_clear_rate,
  and add robust %, human, AUROC and noop columns to the report and CSV.
- AUROC: population-level post-removal AUROC (rewritten-wm vs rewritten-plain)
  plus a baseline sanity AUROC, via a rank-based Mann-Whitney implementation.
- Human-likeness: pluggable --human-backend (stylometry always on, optional
  lastde/binoculars offline detector, degrade gracefully).
- Recipe mode (--mode recipe): parse/validate strength@intensity recipes,
  compose a recipe end-to-end, Phase 1 intensity sweep + Phase 2 per-weight
  beam search, dominance-based (weight-independent) Pareto frontier, and a
  "Best recipes" report section plus recipes.csv. Recommend a default recipe on
  that frontier; --layer-a-after defaults off.

docs + Makefile: document the new measurements and recipe mode, add
bench-full and bench-semantic targets.

Tests: no-op guard (rewrite + bench), robust-clear accounting, AUROC,
recipe parse/validate, Pareto dominance, compose ordering, human-likeness
fallback, and recipe render/CSV.

* fix(bench): address CodeRabbit review feedback and expand docstring coverage

* build(bench): default rewrite backend to DeepSeek

bench-full and bench-semantic referenced undefined REWRITE_* Make
variables, so they expanded to a dangling '--rewrite-backend
 --rewrite-model ' command. Define them with DeepSeek defaults
(openai-compatible / deepseek-v4-flash / api.deepseek.com + allow-remote),
overridable per-invocation (e.g. REWRITE_BASE_URL=http://127.0.0.1:8000
REWRITE_ALLOW_REMOTE= for a local vLLM).

* fix(bench): address remaining CodeRabbit review feedback

- parse_float_grid: reject an empty intensity grid (SystemExit) so a
  misconfigured --intensity-grid fails fast instead of silently searching
  nothing (comment 6).
- rewrite_text invocation: route the new --noop-lex-floor subprocess value
  through safe_arg() per the service/** path instruction (comment 13).
- Makefile: run bench-full under $(MARKLLM_DIR)/.venv/bin/python (and install
  semantic deps with the same interpreter in bench-semantic) so a
  --require-semantic run actually finds sentence-transformers; fail clearly
  when REWRITE_MODEL/REWRITE_BACKEND are empty (comment 12).
- docs: benchmark recipe example uses ~/MarkLLM/.venv/bin/python so
  --require-semantic resolves (comment 12).

* fix(bench): correct the --noop-lex-floor help text (CodeRabbit #10)

A no-op row keeps before_pos (so it is still in the clear-rate denominator)
but has cleared=None, so it never counts as a clear. The help text said
'excluded from the clear-rate denominator', which was wrong; state that it
never counts as a clear.

---------

Co-authored-by: guillaumemeyer <guillaumemeyer@users.noreply.github.com>
Co-authored-by: Poorvith M P <poorvith007@proton.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant