Correct the release 1.27.0 date by Innavin369 · Pull Request #477 · opensupplyhub/open-supply-hub

Innavin369 · 2025-01-06T16:04:18Z

The release 1.27.0 date has been changed to January 11, 2025.

sonarqubecloud · 2025-01-06T16:04:57Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

coderabbitai · 2025-01-06T16:06:23Z

📝 Walkthrough

Walkthrough

The pull request updates the release notes for Open Supply Hub version 1.27.0, shifting the release date to January 11, 2025. The changes primarily focus on introducing two new PATCH endpoints for moderation events and production locations. These endpoints enable creating contributions for existing production locations and updating production locations with new moderation events. Additionally, the release notes document bug fixes related to date validation, API response sorting, and moderation decision date presentation.

Changes

File	Change Summary
`doc/release/RELEASE-NOTES.md`	- Updated release date to January 11, 2025 - Added new PATCH endpoints for moderation events and production locations - Disabled dynamic mapping for new fields in `moderation-events` index - Documented bug fixes for date validation, sorting, and moderation decision dates

Sequence Diagram

sequenceDiagram
    participant Client
    participant API
    participant ModEvents as Moderation Events
    participant ProdLocation as Production Locations

    Client->>API: PATCH /api/v1/moderation-events/{moderation_id}/production-locations/{os_id}
    API->>ModEvents: Retrieve Moderation Event
    API->>ProdLocation: Create/Update Contribution
    
    Client->>API: PATCH /api/v1/production-locations/{os_id}
    API->>ModEvents: Update with New Moderation Event
    API->>ProdLocation: Update Production Location

Possibly related PRs

[OSDEV-1332] Moderation. Implement PATCH api/v1/moderation-events/{moderation_id} #393: Implements PATCH /api/v1/moderation-events/{moderation_id} endpoint, directly related to the new moderation event PATCH endpoints
[OSDEV-1533] Moderation Decision Date should be N/A if "status_change_date" is absent in object #468: Updates the presentation of Moderation Decision Date to display "N/A" when "status_change_date" is absent

Suggested reviewers

roman-stolar
mazursasha1990
VadimKovalenkoSNF
vladsha-dev

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c6eb08a and 3379050.

📒 Files selected for processing (1)

doc/release/RELEASE-NOTES.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (13)

GitHub Check: run-integration-test-code-quality
GitHub Check: run-flake8-linter
GitHub Check: run-fe-code-quality
GitHub Check: run-eslint-linter-and-prettier-formatter
GitHub Check: run-django-code-quality
GitHub Check: run-dd-code-quality
GitHub Check: run-countries-code-quality
GitHub Check: run-contricleaner-code-quality
GitHub Check: get-base-branch-fe-cov
GitHub Check: get-base-branch-django-cov
GitHub Check: get-base-branch-countries-cov
GitHub Check: get-base-branch-dd-cov
GitHub Check: get-base-branch-contricleaner-cov

🔇 Additional comments (3)

doc/release/RELEASE-NOTES.md (3)

10-10: LGTM! Release date update looks good.

The release date has been correctly updated to January 11, 2025, following the consistent date format used throughout the document.

Line range hint 1-24: LGTM! Document structure and formatting are consistent.

The release notes maintain proper markdown formatting and follow the established structure from previous releases, with clear section headers and consistent indentation.

🧰 Tools

🪛 Markdownlint (0.37.0)

13-13: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)

Line range hint 13-24: LGTM! Technical content is accurate and well-documented.

The release notes effectively document:

Two new PATCH endpoints with clear purposes

Changes to OpenSearch index configuration

Specific bugfixes with corresponding JIRA tickets

🧰 Tools

🪛 Markdownlint (0.37.0)

13-13: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

barecheck · 2025-01-06T16:06:51Z