Next.js 13

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update golang docker tag to v1.22.3
• chore(deps): update redis docker tag to v7.2.5
• fix(deps): update module github.com/swaggo/swag to v1.16.3
• fix(deps): update module github.com/xuri/excelize/v2 to v2.8.1
• chore(deps): update alpine docker tag to v3.20
• chore(deps): update dependency @types/yup to ^0.32.0
• chore(deps): update dependency eslint to v8.57.0
• chore(deps): update dependency eslint-plugin-react to v7.34.2
• chore(deps): update dependency prettier to v3.3.0
• chore(deps): update dependency sass to v1.77.4
• chore(deps): update node.js to v20.13.1 (node, @types/node)
• chore(deps): update postgres docker tag to v16.3
• chore(deps): update sosedoff/pgweb docker tag to v0.15.0
• fix(deps): update dependency framer-motion to v11.2.10
• fix(deps): update dependency react-icons to v4.12.0
• fix(deps): update module github.com/gin-gonic/gin to v1.10.0
• fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.1
• fix(deps): update module github.com/golang-migrate/migrate/v4 to v4.17.1
• fix(deps): update module github.com/jackc/pgx/v5 to v5.6.0
• fix(deps): update module github.com/redis/go-redis/v9 to v9.5.2
• fix(deps): update module github.com/spf13/viper to v1.19.0
• fix(deps): update module go.uber.org/zap to v1.27.0
• chore(deps): update actions/cache action to v4
• chore(deps): update actions/setup-go action to v5
• chore(deps): update dependency @typescript-eslint/eslint-plugin to v7
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency vercel to v34
• fix(deps): update dependency date-fns to v3
• fix(deps): update dependency react-icons to v5
• fix(deps): update module github.com/swaggo/files to v2
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update nextjs monorepo to v14.2.3 (eslint-config-next, next)
• fix(deps): update dependency @chakra-ui/theme-tools to v2.1.2
• fix(deps): update dependency swr to v2.2.5
• chore(deps): update dependency @cloudflare/next-on-pages to v1.11.3
• chore(deps): update dependency @typescript-eslint/eslint-plugin to v6.21.0
• chore(deps): update dependency typescript to v5.4.5
• chore(deps): update react monorepo (@types/react, @types/react-dom, react, react-dom)
• fix(deps): update dependency axios to v1.7.2
• fix(deps): update dependency jotai to v2.8.2
• fix(deps): update dependency yup to v1.4.0
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

swag

Swag converts Go annotations to Swagger Documentation 2.0. We've created a variety of plugins for popular Go web frameworks. This allows you to quickly integrate with an existing Go project (using Swagger UI).

fiber document: gofiber website

reason

Since Fiber is built on top of Fasthttp, your apps will enjoy unmatching performance!

As a product manager, I want to provide users with the ability to download their blood pressures to an Excel file, so that they can easily analyze and track their health data.

User Story:

As a user, I want to be able to download my blood pressures to an Excel file, so that I can analyze and track my health data more effectively.

Acceptance Criteria:

1. As a user, I should be able to initiate the download process to generate an Excel file containing the blood pressures.
2. The Excel file should be created using the excelize library.
3. The Excel file should include the following columns: Date, Time, Systolic Pressure, Diastolic Pressure, and Heart Rate.
4. The blood pressures should be sorted in ascending order based on the date and time.
5. The Excel file should be named in a user-friendly format, such as "User_Blood_Pressures.xlsx".

Additional Considerations:

The download functionality should be easily accessible within the user interface, such as through a button or a menu option.
Error handling should be implemented to handle cases where there are no blood pressures recorded for the selected user.
The download process should be efficient and not cause any significant delays or performance issues.

Note to the developer:

Please ensure that the download functionality is implemented using the excelize library to generate the Excel file. Consider using appropriate APIs and methods provided by the library to create the file and populate it with the blood pressure data.

Goal:

As a user, I want to be able to easily record my weight information to track and manage my health.

Description:

As a health-conscious user, I would like to effortlessly record my weight information in the app to keep track of changes. This will help me better understand my health status and set appropriate health goals.

Acceptance Criteria:

1. When I log into the app, I should be able to find the "Record Weight" option on the main interface or in a dedicated health module.
2. On the "Record Weight" page, I should be able to input my weight information.
3. After entering weight information, I can choose to save or submit to record this weight entry.
4. I should be able to view the historical record of weight information to track trends.
5. The system should provide concise charts or statistics to help me visually understand the trend of weight changes.
6. I would also like to set weight goals and receive relevant reminders or suggestions to help me achieve my health objectives.

gorm is very hard to use. i want to use pgx

Description:

As a developer, I want to upgrade our Next.js application to version 14 in order to benefit from the performance optimizations and feature enhancements of the new version.

User Story:

As a developer, I want to upgrade our Next.js application to version 14 to improve the performance and user experience of our application. To achieve this goal, I need to complete the following tasks:

1. Research the changes and improvements in Next.js version 14 to understand the new features and advantages.
2. Check our application code and dependencies to ensure compatibility with Next.js version 14. If there are any code or dependency issues that are not compatible with the new version, they need to be addressed and updated accordingly.
3. Follow the upgrade guide provided by Next.js to incrementally update our application code and configuration. This may involve updating API calls, adjusting routing configurations, modifying styles, and other necessary changes.
4. Run tests to ensure that our application remains stable and correct after the upgrade to Next.js version 14. This includes unit tests, integration tests, and end-to-end tests to validate the functionality.
5. Perform performance testing and optimization to leverage the performance improvements offered by Next.js version 14, enhancing the loading speed and responsiveness of our application.
6. Update our documentation and training materials to enable team members to quickly understand and adapt to the changes and new features introduced in Next.js version 14.
7. Stay updated with the Next.js community and official documentation to learn about the latest updates and bug fixes in the new version, and apply them to our application in a timely manner.
8. Promote and introduce the improvements and advantages of Next.js version 14 to team members, enhancing the development efficiency and user experience of our team.

Acceptance Criteria:

• The application is successfully upgraded to Next.js version 14 and functions properly.
• The performance of the application is improved, with noticeable enhancements in loading speed and responsiveness.
• Code modifications and configuration adjustments made during the upgrade process are thoroughly tested and do not introduce new bugs or issues.
• Documentation and training materials are updated, enabling team members to quickly understand and adapt to the changes and new features of Next.js version 14.
• Team members are aware of the improvements and advantages of Next.js version 14 and can effectively utilize the new version to enhance development efficiency and user experience.