Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: bump ceramic package versions to 6.x #158

Conversation

smrz2001
Copy link
Collaborator

@smrz2001 smrz2001 commented Aug 5, 2024

Tested against QA and all correctness tests passed.

@smrz2001 smrz2001 requested review from stbrody and 3benbox August 5, 2024 16:28
@smrz2001 smrz2001 self-assigned this Aug 5, 2024
Copy link

linear bot commented Aug 5, 2024

@@ -17,4 +17,4 @@ COPY src/ ./src
# Select all tests by default
ENV TEST_SELECTOR "correctness"

ENTRYPOINT ["/app/entrypoint.sh", "run", "test", "--forceExit", "--testPathPattern", "$TEST_SELECTOR"]
ENTRYPOINT ["/app/entrypoint.sh", "run", "test", "--testPathPattern", "$TEST_SELECTOR"]
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is ok because the test directive in package.json already adds --forceExit to the jest command.

Copy link
Contributor

@3benbox 3benbox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@smrz2001 smrz2001 force-pushed the feature/aes-293-correctness-test-are-failing-typescript-module-failure branch from f0ba646 to 443a3b3 Compare August 5, 2024 17:11
@smrz2001 smrz2001 enabled auto-merge August 5, 2024 17:21
@smrz2001 smrz2001 added this pull request to the merge queue Aug 5, 2024
Merged via the queue into main with commit b9b50e3 Aug 5, 2024
17 checks passed
@smrz2001 smrz2001 deleted the feature/aes-293-correctness-test-are-failing-typescript-module-failure branch August 5, 2024 19:48
@stbrody
Copy link
Collaborator

stbrody commented Aug 6, 2024

huh, I wonder why the tests didn't break right away after we released the 6.x versions, but only broke after a few weeks. I wonder if we have a package somewhere that started depending on the 6.x versions but didn't increase it's own major version as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants