Repository navigation
chore: merge develop into main - #135
Merged
Merged
Conversation
feat(release): #125 publish the dataset from the kind of change
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
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.
Closes #125
Summary
Brings develop to main: the automatic release of the dataset (#126), which picks the version from the kind of change (patch for the BAN points only, minor for any other change of the rows, draft for a major change or more than 1 percent of rows removed). It touches
build-dataset.yml,watch-sources.yml,compare_exports.py,docs/release.mdand the README. Nothing is tagged or released by this merge itself.Scheduled workflows run from the default branch: once this is on main, the daily
Watch sourcesrun (and the weekly BAN control on Monday) uses the new logic and can publish a release by itself, since the release secrets andDATAGOUV_AUTO_PUBLISHare set.Checks
make qualitypasses with no new baseline entry.make testpasses and the coverage does not go down.docs/).type(scope): #TICKET subject.Not validated
Build datasethas no successful run of the new logic: its last two runs on the feature branch (2026-10-26) failed, and the only later run is on main with the previous version.