-
Notifications
You must be signed in to change notification settings - Fork 51
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
Deploy to production #4533
Deploy to production #4533
Conversation
fix(deps): update dependency @pulumi/aws to v6.18.0
chore(deps): update dependency node to v20.11.0
chore(deps): update dependency vimeo/psalm to v5.19.0
fix(deps): update dependency @pulumi/pulumi to v3.101.0
chore(deps): update pulumi/pulumi-nodejs docker tag to v3.101.0
chore(deps): update dependency eslint-plugin-prettier to v5.1.3
chore(deps): update dependency @vitejs/plugin-vue to v5.0.3
This reverts commit cd2f32e.
This reverts commit c5722cf.
This reverts commit 316a9c5.
…ailed If we don't run the job always and do the check ourselves, the job gets skipped.
…kipped CI: fix workflow success can be skipped
…of 2023 for staging
.observability: let top right camp counter cover summer 2024 instead of 2023 for staging and devel
…acking Disable Sentry session tracking
chore(deps): update amazon/aws-cli docker tag to v2.15.9
chore(deps): update pulumi/pulumi-nodejs docker tag to v3.102.0
chore(deps): update dependency @react-pdf/render to v3.4.1
fix(api): mitigate slow queries
chore(deps): update dependency @react-pdf/layout to v3.10.2
fix(deps): update dependency @pulumi/aws to v6.18.2
fix(deps): update dependency isomorphic-dompurify to v2.3.0
chore(deps): update dependency @react-pdf/pdfkit to v3.1.2
fix(api): fixes phpstan & psalm errors
chore(deps): update dependency @react-pdf/layout to v3.10.3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Manually tested print (both layout), tiptap and pages who load from /content_nodes
Looks good to me.
/fast-forward |
I also tested, everything looked fine for me. On the story overview, filtering content nodes by period takes 300-400ms now instead of 8-12 seconds previously. |
No blog post is needed I think. Changes are only internal and performance related. Also, Sentry session tracking is disabled now. The community contribution can be mentioned in the blog post for the next bigger release.