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.

Sign up for GitHub

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

Jump to bottom

Update Postgres to 16.1 #474

Closed
derTobsch opened this issue Nov 29, 2023 · 0 comments · Fixed by #475
Closed

Update Postgres to 16.1 #474

derTobsch opened this issue Nov 29, 2023 · 0 comments · Fixed by #475
Labels
status: planned This issue is planned in a milestone and won't be touched by stale bot.
Milestone
2.0.0

Comments

@derTobsch
Copy link
Contributor

Upgrade postgresql to 16.1
@derTobsch derTobsch added the status: new Initial state for every issue / pullrequest label Nov 29, 2023
@derTobsch derTobsch added this to the 2.x milestone Nov 29, 2023
@github-actions github-actions bot added status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: new Initial state for every issue / pullrequest labels Nov 29, 2023
@derTobsch derTobsch mentioned this issue Nov 29, 2023
Merged
3 tasks
@derTobsch derTobsch modified the milestones: 2.x, 2.0.0 Nov 29, 2023
@github-actions github-actions bot added status: new Initial state for every issue / pullrequest status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: planned This issue is planned in a milestone and won't be touched by stale bot. status: new Initial state for every issue / pullrequest labels Nov 29, 2023
derTobsch added a commit that referenced this issue Nov 29, 2023
@derTobsch
Upgrade postgresql to 16.1 (#475)
4eee2be 
closes #474 

Here are some things you should have thought about:

**Multi-Tenancy**
- [ ] Extended new entities with `AbstractTenantAwareEntity`?
- [ ] New entity added to `TenantAwareDatabaseConfiguration`?
- [ ] Tested with `dev-multitenant` profile?

<!--

Thanks for contributing to the zeiterfassung.
Please review the following notes before submitting you pull request.

Please look for other issues or pull requests which already work on this
topic. Is somebody already on it? Do you need to synchronize?

# Security Vulnerabilities

🛑 STOP! 🛑 If your contribution fixes a security vulnerability, please do
not submit it.
Instead, please write an E-Mail to [email protected] with all the
information
to recreate the security vulnerability.

# Describing Your Changes

If, having reviewed the notes above, you're ready to submit your pull
request, please
provide a brief description of the proposed changes.

If they:
🐞 fix a bug, please describe the broken behaviour and how the changes
fix it.
    Please label with 'type: bug' and 'status: new'
    
🎁 make an enhancement, please describe the new functionality and why you
believe it's useful.
    Please label with 'type: enhancement' and 'status: new'
 
If your pull request relates to any existing issues,
please reference them by using the issue number prefixed with #.

-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: planned This issue is planned in a milestone and won't be touched by stale bot.
Projects
None yet
Milestone
2.0.0
Development

Successfully merging a pull request may close this issue.

Upgrade postgresql to 16.1 urlaubsverwaltung/zeiterfassung
1 participant
@derTobsch