Update MANIFEST.in to include migration files and public assets #174
Conversation
This file contains 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
|
@avdata99 the official policy of CKAN is to only support the latest 2 mayor versions. Feel free to drop any reference/support for CKAN 2.9 |
avdata99
force-pushed
the
missing_install_files
branch
from
643c452 to
1862ab5
Compare
|
@pdelboca CKAN 2.9 support dropped |
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.
If possible, please release a new tag/version
Test for CKAN 2.9 started failing due to a setptools conflicts
After fixing that, a solr9 schema error appears
The tests were divided into two files
A new approach with lates version only compatible with latest CKAN and older version branches here compatible with older CKAN version will dramatically reduce times for PRs here.
It's always possible to backport new features for older version branches