MAINT: Use spin lint in CI#25103
Conversation
ganesh-k13
left a comment
There was a problem hiding this comment.
Need to add spin as a lint requirement now. Would it make sense to merge linter_requirements.txt with build_requirements.txt now? Since lint checks should technically be part of the development workflow?
|
+1 for keeping separate, |
bcabf55 to
e716d50
Compare
17ee666 to
e716d50
Compare
f172c7f to
79e72dd
Compare
|
@ganesh-k13 will you be continuing with this? There are merge conflicts |
|
Yeah, I'll look into it to see if it's still a valid enhancement this week. |
79e72dd to
2814d15
Compare
e6c5b07 to
07ea700
Compare
- use `spin lint` for CI - use `spin notes` for CI
07ea700 to
1ed690f
Compare
1ed690f to
c204338
Compare
|
Circle CI is passing as well |
| . venv/bin/activate | ||
| VERSION=$(pip show numpy | grep Version: | cut -d ' ' -f 2 | cut -c 1-5) | ||
| spin notes --version-override $VERSION | ||
|
|
There was a problem hiding this comment.
I think spin docs creates the release notes, no?
There was a problem hiding this comment.
I did a simple check:
$ spin docs -j8
Invoking `build` prior to building docs:
$ /<>/Documents/os/np-test/bin/python3 vendored-meson/meson/meson.py compile -C build
INFO: autodetecting backend as ninja
...
$ git status
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
$ spin notes
Generating release notes for NumPy 2.5.0.dev0
Reading upcoming changes from doc/release/upcoming_changes/
$ towncrier build --version 2.5.0.dev0 --yes
Loading template...
Finding news fragments...
Rendering news fragments...
...
$ git status
On branch main
Your branch is up to date with 'origin/main'.
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
deleted: doc/release/upcoming_changes/29536.deprecation.rst
deleted: doc/release/upcoming_changes/30181.deprecation.rst
deleted: doc/release/upcoming_changes/30340.expired.rst
deleted: doc/release/upcoming_changes/30381.new_feature.rst
deleted: doc/release/upcoming_changes/30460.expired.rst
deleted: doc/release/upcoming_changes/30461.expired.rst
deleted: doc/release/upcoming_changes/30462.expired.rst
deleted: doc/release/upcoming_changes/30463.expired.rst
deleted: doc/release/upcoming_changes/30467.expired.rst
deleted: doc/release/upcoming_changes/30480.typing.rst
deleted: doc/release/upcoming_changes/30489.compatibility.rst
deleted: doc/release/upcoming_changes/30517.performance.rst
deleted: doc/release/upcoming_changes/30538.change.rst
deleted: doc/release/upcoming_changes/30566.typing.rst
deleted: doc/release/upcoming_changes/30604.expired.rst
deleted: doc/release/upcoming_changes/30605.deprecation.rst
deleted: doc/release/upcoming_changes/30610.expired.rst
deleted: doc/release/upcoming_changes/30612.expired.rst
deleted: doc/release/upcoming_changes/30613.expired.rst
deleted: doc/release/upcoming_changes/30614.expired.rst
deleted: doc/release/upcoming_changes/30644.deprecation.rst
deleted: doc/release/upcoming_changes/30653.new_feature.rst
deleted: doc/release/upcoming_changes/30707.change.rst
The release notes are not getting generated in spin docs
There was a problem hiding this comment.
But this is interesting
Lines 115 to 117 in dd6a3ad
There was a problem hiding this comment.
Ok so --keep and --draft (ref) does not write to the output files. But it gets the checks done and will fail if there are errors. So we can remove this.
spin commands for CIspin commands for CI

Changes
spin lintfor CIuse spin notes for CITesting
Notes
spincommands for developer workflow #24080lintspin command #24983ENH: Addednotescommand for spin #25017