-
Notifications
You must be signed in to change notification settings - Fork 48
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 staging #4749
Merged
Deploy to staging #4749
Conversation
This file contains 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 dependency @types/node to v20.11.15
chore(deps): update pulumi/pulumi-nodejs docker tag to v3.104.2
fix(deps): update dependency @pulumi/pulumi to v3.104.2
We don't need to sort because all schedule entries of the period are fetched when printing is started, and the schedule entries of a period are ordered correctly when fetching from the API. This might become relevant again far in the future if we introduce more offline functionality. For now, the sorting was incorrect anyways, because it assumed that the scheduleEntryNumber was unique per day, which it isn't (there can be multiple numbering schemes leading to multiple of the same scheduleEntryNumbers on the same day).
chore(deps): update dependency @types/node to v20.11.16
chore(deps): update dependency @nuxtjs/i18n to v8.0.1
chore(deps): update dependency @sentry/vite-plugin to v2.11.0
This snapshot was flawed because of the wrong sorting before. There are some schedule entries with numberingScheme 'A' in the store data, and these were previously incorrectly sorted: dayNumber scheduleEntryNumber number startTime 1 1 1.1 08:00 1 2 1.2 09:00 1 1 1.A 10:00 The last one was previously sorted before the second one, which is incorrect.
chore(deps): update dependency @sentry/vite-plugin to v2.13.0
fix(deps): update dependency puppeteer-core to v21.11.0
…assertions-5.x chore(deps): update dependency spatie/phpunit-snapshot-assertions to v5.1.4
chore(deps): update dependency @nuxtjs/tailwindcss to v6.11.3
chore(deps): update amazon/aws-cli docker tag to v2.15.17
fix(deps): update dependency html-entities to v2.5.2
chore(deps): update dependency vite to v5.1.5
chore(deps): lock file maintenance
chore(deps): lock file maintenance
We use eCamp v3 for our instance, and ecamp3 for the source code repository, but never eCamp3
chore(deps): lock file maintenance
chore(deps): lock file maintenance
Consistent project naming
chore(deps): lock file maintenance
Else the queries are executed without a user filter, which keeps our database busy.
api: restrict access to protected routes with firewall
Treat camps as past only after last day is over
chore(deps): update pulumi/pulumi-nodejs docker tag to v3.109.0
carlobeltrame
approved these changes
Mar 8, 2024
simfeld
approved these changes
Mar 8, 2024
manuelmeister
approved these changes
Mar 9, 2024
/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.
Mainly for
But also with: