@bendhouseart ok, solved that issue

Codecov Report

Merging #1252 (c763bb0) into master (db4b0f5) will increase coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1252      +/-   ##
==========================================
+ Coverage   88.23%   88.33%   +0.09%     
==========================================
  Files           6        6              
  Lines        1020     1020              
==========================================
+ Hits          900      901       +1     
+ Misses        120      119       -1     

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@effigies @bendhouseart

ok, so at long last this is done. To recap:

• Depending on the BIDSSCHEMATOOLS_RELEASE envvar being set, one of our tests will create a testdata copy directory which is not torn down (this was already in).
• Now, however, the directory for this archive is bidsschematools/tests/data/bundled.
• We set this variable depending on whether or not the first seven characters of the tag are schema-
• If the variable is set we build the package — including testdata, which is less than 1MB compressed and 2.7 MB uncompressed.
• If the variable is set we test the upload to test.pypi
• If the variable is set and the test upload succeeded we upload to pypi
• we now have a script which should make testing for and development of tag-based hooks easier inside (scripts/test_tag)

For this PR to actually do anything at all, an additional 2 commits will be required after merge by someone who knows what our secrets are called:

1. set tokens:

• replaces secrets.BIDS_TOKEN_TEST in the “Real Upload” section to whatever the BIDS pypi token is called.
• replaces secrets.BIDS_TOKEN_TEST in the “Test Upload” section to whatever the BIDS test.pypi token is called.
• alternatively you can give me permissions to upload dedicated tokens for the both
• optionally we can remove the autodata2 branch entry from the head of .github/workflows/schemacode_ci.yml

2. trigger release:

• remove -dev from src/schema/SCHEMA_VERSION
• add a tag called schema-0.4.0

@effigies should be good to go. Thanks for your help. If you squash you can also add @bendhouseart as co-author since he helped as well.

0.4.0 is up on PyPI.

Amazing, just tested it, works system-wide via Gentoo and passes all tests :3

https://ppb.chymera.eu/5a3281

@bendhouseart ok, solved that issue

That looked nasty.