release: civiccore v1.2.1 (publish the local-task-queue migration line) - #68
Merged
Conversation
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.
Bumps civiccore to v1.2.1 so the
civiccore_0003_local_task_queuemigration (and the Windows-local platform contracts on main) ship as a PUBLISHED package. The v1.2.0 wheel predates that migration, which is why downstream module tests that expect migration headciviccore_0003_local_task_queuefail against the published wheel (e.g. civicclerk's alembic upgrade test). After this merges, a v1.2.1 release + wheel is cut and the city-core modules repoint their civiccore pin to it.