You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling this a bug instead of a feature due to the potential security and breaking UX implications of pulling from master.
To avoid breaking nodebuilder whenever dependencies need to change, have the user run nodebuilder with the most recent version tag (which we already do) that also downloads runtime dependencies from the most recent version tag (which we don't do right now).
Same with the Dockerfiles, have them do have them pull from master.
Actual Behavior
Right now dependencies are pulled from master branch, both in the main script and in the Dockerfiles.
Steps to Reproduce
Optional Screenshots
No response
Optional Logs
No response
Operating System
No response
Operating System version
No response
The text was updated successfully, but these errors were encountered:
bitcoin-tools
changed the title
[BUG] - runtime dependencies should pull from most recent tag, not master
[BUG] - dependencies should pull from most recent tag, not master
May 19, 2024
Expected Behavior
Calling this a bug instead of a feature due to the potential security and breaking UX implications of pulling from
master
.To avoid breaking nodebuilder whenever dependencies need to change, have the user run nodebuilder with the most recent version tag (which we already do) that also downloads runtime dependencies from the most recent version tag (which we don't do right now).
Same with the Dockerfiles, have them do have them pull from master.
Actual Behavior
Right now dependencies are pulled from master branch, both in the main script and in the Dockerfiles.
Steps to Reproduce
Optional Screenshots
No response
Optional Logs
No response
Operating System
No response
Operating System version
No response
The text was updated successfully, but these errors were encountered: