Skip to content

Commit

Permalink
fix: g2p main is about to be 2.0, but we still want 1.1 on Heroku
Browse files Browse the repository at this point in the history
We had changed things so Heroku builds always took origin/main for g2p,
but now that we're working on g2p 2.0 with breaking changes, we have to
revert this change and get the latest g2p 1.1.* release instead.

Fixes #186
  • Loading branch information
joanise authored and roedoejet committed Sep 11, 2023
1 parent 9a526c2 commit adfe51f
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 3 deletions.
2 changes: 0 additions & 2 deletions requirements.api.txt
Original file line number Diff line number Diff line change
Expand Up @@ -3,5 +3,3 @@
gunicorn
# uvicorn works on all platforms and is required for both dev and prod deployments
uvicorn
# For deployment on Heroku, we want the latest g2p off GitHub
g2p @ git+https://github.com/roedoejet/g2p.git@main
2 changes: 1 addition & 1 deletion requirements.min.txt
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ chevron==0.14.0
click>=8.0.4
coloredlogs==10.0
fastapi==0.78.0
g2p>=1.1.20230511, ==1.*
g2p>=1.1.20230822, ==1.*
lxml==4.9.1
networkx>=2.5,<=2.8.4
numpy>=1.16.4
Expand Down

0 comments on commit adfe51f

Please sign in to comment.