-
Notifications
You must be signed in to change notification settings - Fork 767
WEB-389: Fix date format issue when editing holidays #2741
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
Open
AnvayKharb
wants to merge
1
commit into
openMF:dev
Choose a base branch
from
AnvayKharb:WEB-389-editing-existing-holidays-fails-due-to-date-format-problem
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+23
−16
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify that Docker image version updates align with PR objectives and are secure.
The Dockerfile updates the base images (
node:24-alpine3.22andnginx:1.29-alpine3.22-slim), but the PR description focuses on date formatting fixes for holiday components and does not mention Docker changes. This appears to be either an accidental inclusion or an undocumented infrastructure update.Additionally, since the knowledge cutoff is March 2025 and today is November 2025, I need to verify that these specific versions are current, stable, and free of security vulnerabilities.
Please confirm:
Run the following script to check for known security advisories:
🏁 Script executed:
Length of output: 393
I need to verify the stability and security of these image versions through web search rather than direct registry queries.
Consider using nginx stable branch (1.28) instead of mainline (1.29).
The Docker image updates introduce security and stability considerations:
Node.js 24 has officially entered Long-Term Support (LTS) as of October 31, 2025 and will receive maintenance and security updates through April 2028, making
node:24-alpine3.22a secure choice for production builds.However, nginx 1.29 is the mainline branch where latest features and bug fixes get added, denoted by an odd second version number, whereas the stable branch uses even version numbers (e.g., 1.28) and receives only high-severity bug fixes without new features. For a production SPA server, the stable branch is more appropriate. Additionally, nginx 1.29.1+ patches CVE-2025-53859 but versions prior are vulnerable, so pinning to
1.29without a patch version carries security risk.Alpine 3.22 is supported for 2 years, making it a stable base image.
The PR description mentions date formatting fixes for holiday components—verify whether Docker changes are intentional or incidental infrastructure updates.
🤖 Prompt for AI Agents