-
Notifications
You must be signed in to change notification settings - Fork 666
syncpack was failing without logs #7657
Copy link
Copy link
Open
Labels
library: google-cloud-node-coreIssues transferred from another repositoryIssues transferred from another repositorypriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Metadata
Metadata
Assignees
Labels
library: google-cloud-node-coreIssues transferred from another repositoryIssues transferred from another repositorypriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
originally, the intent behind using syncpack was to make sure our dependencies were compatible. but it's been failing on all of our PRs without any logs, and it's difficult to recreate locally (example): https://github.com/googleapis/google-cloud-node-core/actions/runs/22781070422/job/66086734223?pr=920
I think right now it's doing more harm than good but so I'm going to delete it. but, i still think we should come up with some replacement to make sure our dependencies are in sync.