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

Last part of 2.0 (Update database migration and history retention) #5075

Draft
wants to merge 28 commits into
base: master
Choose a base branch
from

Conversation

louislam
Copy link
Owner

@louislam louislam commented Sep 1, 2024

Tick the checkbox if you understand [x]:

  • I have read and understand the pull request rules.

Description

Trying to pick up this project again and finish the last part of 2.0

  • Migrate existing heartbeat data into aggregate tables
  • History retention

Related issue: #4500

Checklist

  • My code follows the style guidelines of this project
  • I ran ESLint and other linters for modified files
  • I have performed a self-review of my own code and tested it
  • I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
  • My changes generates no new warnings
  • My code needed automated testing. I have added them (this is optional task)

@CommanderStorm CommanderStorm added priority:high High Priority releaseblocker blocking bugs encountered with a new release area:core issues describing changes to the core of uptime kuma labels Sep 14, 2024
@CommanderStorm CommanderStorm added this to the 2.0.0 milestone Sep 14, 2024
# Conflicts:
#	server/database.js
#	server/jobs/clear-old-data.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core issues describing changes to the core of uptime kuma priority:high High Priority releaseblocker blocking bugs encountered with a new release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants