Deploy to prod #7201
Merged
Deploy to prod #7201
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chore(deps): update amazon/aws-cli docker tag to v2.24.27
chore(deps): lock file maintenance
fix(deps): update sentry-javascript monorepo to v9.7.0
chore(deps): update amazon/aws-cli docker tag to v2.25.0
chore(deps): update varnish docker tag to v7.7.0
fix(deps): update dependency axios to v1.8.4
chore(deps): update dependency @types/node to v22.13.11
fix(deps): update dependency @pulumi/aws to v6.73.0
chore(deps): update amazon/aws-cli docker tag to v2.25.1
chore(deps): update dependency @eslint/eslintrc to v3.3.1
chore(deps): update eslint monorepo to v9.23.0
It was a little tricky, but finally i figured out how to do it: https://api-platform.com/docs/core/errors/ The big impact is, that the serialization of the errors is now done with the same infrastructure as serializing entities. That makes it less format dependent. It seems a little weird that we use a provider to "replace" the exception path of the response by extracting the exception to the context, and then continuing like when we would serialize a response. But i can also see the benefits. See api-platform/core#5974 Issue: #6618
nginx seems to better retry failed upstreams again if they are defined as upstreams. Without the paid subscription we don't have a health_checks or even new resolves https://docs.nginx.com/nginx/admin-guide/load-balancer/http-health-check/ https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/#configuring-http-load-balancing-using-dns
…ities That we can cache the endpoint.
…nish-url chore: change varnish log output to escapedUrl format
api: offer activities collection under subresource /camps/{:id}/activ…
…not-embed-rootcontentnode activity & category, do not embed rootContentNode
…ivity Avoid duplicate GET activity in activity view
pmattmann
approved these changes
Apr 12, 2025
manuelmeister
requested changes
Apr 12, 2025
is only on the pull request |
manuelmeister
approved these changes
Apr 12, 2025
|
/fast-forward |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.