While developing solutions for software-issues №55 and roundup-action №124, I struggled to comprehend why the Roundup Action seemingly has been functioning fine in the NASA-PDS organization but not in the sandbox—even after sync'ing to the sandbox.
The issue: the production organization's stable tag was still pointing to an older release which never transitioned away from pds-github-util and towards the lasso-* monopoly-breakup packages. Further, some transitive and unpinned dependencies seemingly have evolved in the intervening time—and this broke the Roundup Action on main and in the sandbox.
Merge this to bring things back into check, namely by addressing:
Container setup was giving different results from python setup.py install and pip install .; but the former is obsolete anyway so switch to the latter
The comment about setup.cfg requirements was incorrect; those were in fact being used during container setup
Pin the requirements in setup.cfg to conform to those in github-actions-base as well as lasso-releasers and lasso-requirements
Use the correct "internal anatomy" of lasso-releasers, not pds-github-util
👉 Note: Once this is merged, the pivotal step of moving the stable tag must be done so that these changes will actually take effect for all non-sandbox repositories.
⚙️ Test Data and/or Report
See successful roundups of these two repositories:
🗒️ Summary
While developing solutions for software-issues №55 and roundup-action №124, I struggled to comprehend why the Roundup Action seemingly has been functioning fine in the NASA-PDS organization but not in the sandbox—even after sync'ing to the sandbox.
The issue: the production organization's
stabletag was still pointing to an older release which never transitioned away frompds-github-utiland towards thelasso-*monopoly-breakup packages. Further, some transitive and unpinned dependencies seemingly have evolved in the intervening time—and this broke the Roundup Action onmainand in the sandbox.Merge this to bring things back into check, namely by addressing:
python setup.py installandpip install .; but the former is obsolete anyway so switch to the lattersetup.cfgrequirements was incorrect; those were in fact being used during container setupsetup.cfgto conform to those ingithub-actions-baseas well aslasso-releasersandlasso-requirementslasso-releasers, notpds-github-util👉 Note: Once this is merged, the pivotal step of moving the
stabletag must be done so that these changes will actually take effect for all non-sandbox repositories.⚙️ Test Data and/or Report
See successful roundups of these two repositories:
♻️ Related Issues
No issue was formally filed for this particular problem; it came about while addressing software-issues â„–55 and roundup-action â„–124.