publish heroku should default to currently tagged version
Open
Nobody has claimed this yet.
datasette-publish
- Dominant language
- Python
- Stars
- 11.5k
- Forks
- 904
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 18
Description
Had a report that deploying to Heroku was using the previously installed version of Datasette, not the latest.
Could be because of this:
Heroku documentation recommends pinning to specific versions https://devcenter.heroku.com/articles/python-pip
So... we could ensure we default to an install value of ["datasette>=current_tag"].
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in datasette/publish/heroku.py at lines 172-179 and inspect how the Heroku publish command chooses its Datasette install value. Verify the default uses the currently tagged version rather than a previously installed one, then exercise the Heroku publish path to confirm the generated installation setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100