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
We need to ensure the hubcap script is prepared to handle packages with main, then prioritize that if there's no master branch. Currently, master is hardcoded into the script. We need main conditional logic that uses main then master when looking for commit shas to change into package specs. Otherwise, newer versions won't be added to hub.getdbt.com; the script will just break for any repo that does not retain a master branch.
Good news though! Because package specs depend only on commit shas, nothing has been changed for previous versions of packages.
The text was updated successfully, but these errors were encountered:
VersusFacit
changed the title
Urgent: Build package configs from main branch (or master)
Bug: Build package configs from main branch (or master)
Sep 13, 2021
VersusFacit
changed the title
Bug: Build package configs from main branch (or master)
[Urgent] Bug: Build package configs from main branch (or master)
Sep 13, 2021
We need to ensure the hubcap script is prepared to handle packages with main, then prioritize that if there's no master branch. Currently, master is hardcoded into the script. We need main conditional logic that uses main then master when looking for commit shas to change into package specs. Otherwise, newer versions won't be added to hub.getdbt.com; the script will just break for any repo that does not retain a master branch.
Good news though! Because package specs depend only on commit shas, nothing has been changed for previous versions of packages.
This will partially address issue #69 .
The text was updated successfully, but these errors were encountered: