Repository navigation
chore: prepare 0.2.0 - #6
Merged
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
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.
This gets the repo ready for 0.2.0. It bumps the version to 0.2.0 and dates the changelog entry, including a short "Upgrading from 0.1.0" note about the bigger default search (15 sources, about 20 seconds cold), the new
kindfield and the lazyRmiSource.fetch(). It also fixes Kiryat Motzkin: 24 of its 29 rows were pages about the tender committee (meetings and protocols), not tenders, and they are now left out, so the city shows its 3 real tenders. I checked the result against the live site today. Everything passes locally, including the 16 live tests, and the 0.2.0 wheel builds and passes twine check. I have not tagged anything.