html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,issue,performed_via_github_app
https://github.com/simonw/datasette/issues/2006#issuecomment-1405488884,https://api.github.com/repos/simonw/datasette/issues/2006,1405488884,IC_kwDOBm6k_c5Txg70,9599,2023-01-26T19:20:53Z,2023-01-26T19:20:53Z,OWNER,I can run a GitHub code search a week or so before the release to give me time to get in touch with anyone who has actions that look like they might break.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",1558644003,
https://github.com/simonw/datasette/issues/2006#issuecomment-1405488523,https://api.github.com/repos/simonw/datasette/issues/2006,1405488523,IC_kwDOBm6k_c5Txg2L,9599,2023-01-26T19:20:32Z,2023-01-26T19:20:32Z,OWNER,"This won't actually help that much if the user's GitHub Actions workflow does the equivalent of this:
```
pip install datasette
datasette publish cloudrun mydb.db ...
```
Since they'll get the 1.0 release too.

Since they'll need to make changes anyway, maybe a better solution is to document this and tell people they should use this instead:

```
datasette publish cloudrun mydb.db ... --branch 0.64.1
```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",1558644003,