Closed pdurbin closed 4 months ago
After the following PR was merged...
... npm run test:integration tests were failing if you switch test/environment/.env to a branch that was built before the PR was merged. For example:
npm run test:integration
test/environment/.env
DATAVERSE_IMAGE_REGISTRY=ghcr.io DATAVERSE_IMAGE_TAG=add-isreleased-field-to-get-dataverse-api-response
This is because...
add-isreleased-field-to-get-dataverse-api-response
As of this pull request, we switch configbaker to use the same tag as the dataverse image so they'll be compatible.
Tested with @ekraffmiller looking over my shoulder.
If you are curious what the failure looked like (You must be a superuser to change this setting), see this PR:
You must be a superuser to change this setting
Test test/environment/.env with variations:
No.
What this PR does / why we need it:
After the following PR was merged...
...
npm run test:integration
tests were failing if you switchtest/environment/.env
to a branch that was built before the PR was merged. For example:This is because...
add-isreleased-field-to-get-dataverse-api-response
image doesn't have it (too old)As of this pull request, we switch configbaker to use the same tag as the dataverse image so they'll be compatible.
Which issue(s) this PR closes:
Related Dataverse PRs:
Special notes for your reviewer:
Tested with @ekraffmiller looking over my shoulder.
If you are curious what the failure looked like (
You must be a superuser to change this setting
), see this PR:Suggestions on how to test this:
Test
test/environment/.env
with variations:Is there a release notes update needed for this change?:
No.
Additional documentation:
No.