Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add constraints.txt make goal #662

Merged
merged 1 commit into from
Aug 18, 2022
Merged

Add constraints.txt make goal #662

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,5 +163,13 @@ publish-multiarch-dev:
-t $(IM):dev \
.

constraints.txt: requirements.txt.full
rm -rf ./tmpdir &&\
virtualenv tmpdir &&\
. tmpdir/bin/activate &&\
python3 -m pip install pip -U &&\
python3 -m pip install -r requirements.txt.full &&\
python3 -m pip freeze > constraints.txt

clean-tests:
rm -rf target/*
2 changes: 1 addition & 1 deletion README-developers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ log to determine if any modifications have been made?
## General SOP for ODK release and publication

* Put the `master` branch in the state we want for release (i.e. merge any approved PR that we want included in that release, etc.).
* Update the [constraits.txt file](https://github.com/INCATools/ontology-development-kit/pull/476#issuecomment-924050937)
* Update the [constraits.txt file](https://github.com/INCATools/ontology-development-kit/pull/476#issuecomment-924050937), with `make constraints.txt`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: constraits.txt -> constraints.txt

* Do any amount of testing as needed to be confident we are ready for release (at the very least, do a local build with `make build` and run the test suite with `make tests`; possibly run some mock releases on known ontologies such as `FBbt`, etc.).
* Tag the release and push the tag to GitHub and create a formal release from the newly pushed tag.
* Run `docker login` to ensure you are logged in. You must have access rights to `obolibrary` organisation to run the following.
Expand Down
Loading