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

fix site url #1

Open
wants to merge 4 commits into
base: old
Choose a base branch
from
Open

fix site url #1

wants to merge 4 commits into from

Conversation

NxPKG
Copy link
Contributor

@NxPKG NxPKG commented Dec 6, 2024

User description

Notes for Reviewers

This PR fixes #

Signed commits

  • Yes, I signed my commits.

PR Type

Bug fix


Description

  • Updated the site URL in the README.md file to point to https://releaselog.netlify.app.
  • Modified the Jekyll configuration file _config.yml to reflect the new site URL.
  • Changed the server URL in the OpenAPI configuration file assets/openapi.yml to the new URL.

Changes walkthrough 📝

Relevant files
Documentation
README.md
Update site URL in README                                                               

README.md

  • Updated the site URL from https://release-parser to
    https://releaselog.netlify.app.
  • +1/-1     
    Configuration changes
    _config.yml
    Update site URL in Jekyll configuration                                   

    _config.yml

    • Changed the url setting to https://releaselog.netlify.app.
    +1/-1     
    openapi.yml
    Update server URL in OpenAPI configuration                             

    assets/openapi.yml

    • Updated server URL to https://releaselog.netlify.app.
    +1/-1     

    💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

    Summary by CodeRabbit

    Release Notes

    • Documentation Updates

      • Updated URLs in the README and configuration files to reflect the new site address: https://releaselog.netlify.app.
      • Enhanced API documentation with improved descriptions and updated contact information.
      • Clarified endpoint descriptions for better understanding of API functionalities.
    • Version Updates

      • OpenAPI specification version updated to 3.1.0.
    • Workflow Adjustments

      • Modified GitHub workflows to reflect changes in branch naming and directory paths for repository operations.

    Copy link

    sourcery-ai bot commented Dec 6, 2024

    Reviewer's Guide by Sourcery

    This PR updates the site URL across multiple configuration files, changing it from 'https://release-parser' to 'https://releaselog.netlify.app'. The changes are straightforward URL replacements in the documentation and configuration files.

    No diagrams generated as the changes look simple and do not need a visual representation.

    File-Level Changes

    Change Details Files
    Update site URL across documentation and configuration files README.md
    _config.yml
    assets/openapi.yml

    Tips and commands

    Interacting with Sourcery

    • Trigger a new review: Comment @sourcery-ai review on the pull request.
    • Continue discussions: Reply directly to Sourcery's review comments.
    • Generate a GitHub issue from a review comment: Ask Sourcery to create an
      issue from a review comment by replying to it.
    • Generate a pull request title: Write @sourcery-ai anywhere in the pull
      request title to generate a title at any time.
    • Generate a pull request summary: Write @sourcery-ai summary anywhere in
      the pull request body to generate a PR summary at any time. You can also use
      this command to specify where the summary should be inserted.

    Customizing Your Experience

    Access your dashboard to:

    • Enable or disable review features such as the Sourcery-generated pull request
      summary, the reviewer's guide, and others.
    • Change the review language.
    • Add, remove or edit custom review instructions.
    • Adjust other review settings.

    Getting Help

    Copy link

    coderabbitai bot commented Dec 6, 2024

    Walkthrough

    The changes involve updates to five files: README.md, _config.yml, assets/openapi.yml, .github/workflows/lint.yml, and .github/workflows/update.yml. The README.md and _config.yml files have modified URLs reflecting a new destination. The assets/openapi.yml file includes enhancements in the OpenAPI specification, such as an updated version, server URL, operation IDs, and improved descriptions for API endpoints. Additionally, workflow files have been adjusted to change branch names and update directory paths for repository operations.

    Changes

    File Change Summary
    README.md Updated URL from https://release-parser to https://releaselog.netlify.app; minor text adjustments.
    _config.yml Updated url setting from https://release-parser to https://releaselog.netlify.app.
    assets/openapi.yml Updated OpenAPI version to 3.1.0, server URL to https://releaselog.netlify.app; modified operation IDs and descriptions for API endpoints.
    .github/workflows/lint.yml Changed branch name from main to master in the push event trigger.
    .github/workflows/update.yml Updated paths for cloning and executing commands related to the website repository.

    Poem

    In the meadow, changes bloom,
    URLs shift, dispelling gloom.
    From parser's path to log's delight,
    Clarity shines, oh what a sight!
    With each update, we hop and play,
    Celebrating progress, hip-hip-hooray! 🐇✨


    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 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.

    Copy link

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Documentation Update
    Verify that the new URL is accessible and working properly in production

    Copy link

    PR Code Suggestions ✨

    No code suggestions found for the PR.

    Copy link

    @sourcery-ai sourcery-ai bot left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Hey @NxPKG - I've reviewed your changes - here's some feedback:

    Overall Comments:

    • Please complete the PR description by filling in the issue number this fixes and checking the signed commits checkbox if applicable.
    Here's what I looked at during the review
    • 🟢 General issues: all looks good
    • 🟢 Security: all looks good
    • 🟢 Testing: all looks good
    • 🟢 Complexity: all looks good
    • 🟢 Documentation: all looks good

    Sourcery is free for open source - if you like our reviews please consider sharing them ✨
    Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

    Copy link

    netlify bot commented Dec 6, 2024

    Deploy Preview for releaselog ready!

    Name Link
    🔨 Latest commit 0527b86
    🔍 Latest deploy log https://app.netlify.com/sites/releaselog/deploys/67527d4b1e7b5e00083762b4
    😎 Deploy Preview https://deploy-preview-1--releaselog.netlify.app
    📱 Preview on mobile
    Toggle QR Code...

    QR Code

    Use your smartphone camera to open QR code link.

    To edit notification comments on pull requests, go to your Netlify site configuration.

    Copy link

    @coderabbitai coderabbitai bot left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Actionable comments posted: 0

    🧹 Outside diff range and nitpick comments (2)
    assets/openapi.yml (2)

    Line range hint 17-156: Consider adding rate limiting information

    The API endpoints are well-documented, but there's no information about rate limiting. Consider adding:

    • Rate limit headers in responses
    • Documentation about rate limits
    • Error responses for rate limit exceeded scenarios

    Example addition:

          responses:
            '200':
              description: OK
    +         headers:
    +           X-RateLimit-Limit:
    +             schema:
    +               type: integer
    +             description: Request limit per hour
    +           X-RateLimit-Remaining:
    +             schema:
    +               type: integer
    +             description: Remaining requests for the hour
    +        '429':
    +          description: Too Many Requests
    +          content:
    +            application/json:
    +              schema:
    +                type: object
    +                properties:
    +                  message:
    +                    type: string
    +                    example: Rate limit exceeded

    Line range hint 293-297: Fix type definition for 'link' property

    The link property's type definition needs to be fixed. Currently, it's defined as:

    type: 
    - string
    - 'null'

    This syntax is incorrect for OpenAPI 3.1.0.

    Apply this fix:

              link:
    -           type: 
    -           - string
    -           - 'null'
    +           type: ['string', 'null']
                minLength: 1
                description: 'Link to changelog for the latest release, if available'
    📜 Review details

    Configuration used: CodeRabbit UI
    Review profile: CHILL

    📥 Commits

    Reviewing files that changed from the base of the PR and between 2e78ae8 and bff73c6.

    📒 Files selected for processing (3)
    • README.md (1 hunks)
    • _config.yml (1 hunks)
    • assets/openapi.yml (1 hunks)
    ✅ Files skipped from review due to trivial changes (2)
    • README.md
    • _config.yml
    🔇 Additional comments (1)
    assets/openapi.yml (1)

    14-15: Verify URL consistency across the specification

    The server URL update looks good, but let's ensure this new URL is consistently used throughout the specification.

    ✅ Verification successful

    URL update is consistent across the codebase

    The new URL https://releaselog.netlify.app is consistently used across the codebase, including in configuration files (_config.yml), documentation, and API specifications. The change aligns with the existing production setup.

    🏁 Scripts executed

    The following scripts were executed for the analysis:

    Script:

    #!/bin/bash
    # Description: Check for any remaining references to old URLs in the codebase
    # and verify the new URL is properly configured
    
    # Search for any remaining references to the old URL
    rg -i "release-parser" --type yaml --type md
    
    # Check if the new URL is properly configured in other config files
    rg -i "releaselog.netlify" --type yaml --type md
    

    Length of output: 74249

    NxPKG added 2 commits December 6, 2024 09:52
    Signed-off-by: NxPKG <[email protected]>
    Signed-off-by: NxPKG <[email protected]>
    Copy link

    codiumai-pr-agent-free bot commented Dec 6, 2024

    CI Failure Feedback 🧐

    (Checks updated until commit 0527b86)

    Action: Update data

    Failed stage: Restore update.py failure [❌]

    Failed test name: ""

    Failure summary:

    The action failed due to multiple ProductUpdateError exceptions raised during the execution of
    various scripts. Specifically:

  • aws-lambda.py failed with a ProductUpdateError because no update was detected for aws-lambda.
  • confluence.py failed with a ProductUpdateError because no update was detected for confluence.
  • firefox.py encountered an AttributeError because the find method returned None, leading to a
    ProductUpdateError for firefox.
  • jira.py encountered an AttributeError because the select_one method returned None, leading to a
    ProductUpdateError for jira.
  • kuma.py failed with a ProductUpdateError because no update was detected for kuma.
  • rocket-chat.py failed with a ProductUpdateError because no update was detected for rocket-chat.
  • spring-boot.py failed with a ProductUpdateError because no update was detected for spring-boot.
  • spring-framework.py failed with a ProductUpdateError because no update was detected for
    spring-framework.
  • unrealircd.py failed with a ProductUpdateError because no update was detected for unrealircd.

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    8584:  unexpected table 'name', skipping
    8585:  unexpected table 'runtime lifecycle phase', skipping
    8586:  unexpected table 'name', skipping
    8587:  no update detected for aws-lambda
    8588:  Traceback (most recent call last):
    8589:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/aws-lambda.py", line 8, in <module>
    8590:  with releasedata.ProductData("aws-lambda") as product_data:
    8591:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 129, in __exit__
    8592:  raise ProductUpdateError(message)
    8593:  common.releasedata.ProductUpdateError: no update detected for aws-lambda
    ...
    
    12009:  no data found for confluence at releases/confluence.json
    12010:  Fetching https://www.atlassian.com/software/confluence/download-archives with JavaScript (click_selector = None, wait_until = None)
    12011:  Fetched https://www.atlassian.com/software/confluence/download-archives
    12012:  no update detected for confluence
    12013:  Traceback (most recent call last):
    12014:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/confluence.py", line 8, in <module>
    12015:  with releasedata.ProductData("confluence") as product_data:
    12016:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 129, in __exit__
    12017:  raise ProductUpdateError(message)
    12018:  common.releasedata.ProductUpdateError: no update detected for confluence
    ...
    
    20267:  ##[endgroup]
    20268:  ##[group]firefox
    20269:  start running src/firefox.py for firefox#custom(firefox)
    20270:  loaded data for firefox from releases/firefox.json
    20271:  Fetching ['https://www.mozilla.org/en-US/firefox/releases/']
    20272:  Fetched ['https://www.mozilla.org/en-US/firefox/releases/']
    20273:  Fetching ['https://www.mozilla.org/en-US/firefox/133.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/132.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/132.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/132.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/131.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/131.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/131.0.3/releasenotes/', 'https://www.mozilla.org/en-US/firefox/130.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/130.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/129.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/129.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/129.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.0.3/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.1.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.2.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.3.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.3.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.4.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.5.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.5.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/127.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/127.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/127.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/126.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/126.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/125.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/125.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/125.0.3/releasenotes/', 'https://www.mozilla.org/en-US/firefox/124.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/124.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/124.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/123.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/123.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/122.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/122.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/121.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/121.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/120.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/120.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/119.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/119.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/118.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/118.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/118.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/117.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/117.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/116.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/116.0.1/releasenotes/']
    20274:  Fetched ['https://www.mozilla.org/en-US/firefox/133.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/132.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/132.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/132.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/131.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/131.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/131.0.3/releasenotes/', 'https://www.mozilla.org/en-US/firefox/130.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/130.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/129.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/129.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/129.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.0.3/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.1.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.2.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.3.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.3.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.4.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.5.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/128.5.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/127.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/127.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/127.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/126.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/126.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/125.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/125.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/125.0.3/releasenotes/', 'https://www.mozilla.org/en-US/firefox/124.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/124.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/124.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/123.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/123.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/122.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/122.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/121.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/121.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/120.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/120.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/119.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/119.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/118.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/118.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/118.0.2/releasenotes/', 'https://www.mozilla.org/en-US/firefox/117.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/117.0.1/releasenotes/', 'https://www.mozilla.org/en-US/firefox/116.0/releasenotes/', 'https://www.mozilla.org/en-US/firefox/116.0.1/releasenotes/']
    20275:  an unexpected error occurred while updating firefox data
    20276:  Traceback (most recent call last):
    20277:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/firefox.py", line 32, in <module>
    20278:  date_str = release_notes_soup.find(class_="c-releaselog").get_text()  # note: only works for versions > 25
    20279:  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    20280:  AttributeError: 'NoneType' object has no attribute 'get_text'
    20281:  Traceback (most recent call last):
    20282:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/firefox.py", line 32, in <module>
    20283:  date_str = release_notes_soup.find(class_="c-releaselog").get_text()  # note: only works for versions > 25
    20284:  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    20285:  AttributeError: 'NoneType' object has no attribute 'get_text'
    20286:  The above exception was the direct cause of the following exception:
    20287:  Traceback (most recent call last):
    20288:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/firefox.py", line 23, in <module>
    20289:  with releasedata.ProductData("firefox") as product_data:
    20290:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 124, in __exit__
    20291:  raise ProductUpdateError(message) from exc_value
    20292:  common.releasedata.ProductUpdateError: an unexpected error occurred while updating firefox data
    ...
    
    32626:  ran src/npm.py for jhipster#npm(generator-jhipster), took 0.50s (success=True)
    32627:  ##[endgroup]
    32628:  ##[group]jira
    32629:  deleted releases/jira.json before running scripts
    32630:  start running src/jira.py for jira#custom(jira)
    32631:  no data found for jira at releases/jira.json
    32632:  Fetching https://www.atlassian.com/software/jira/update with JavaScript (click_selector = None, wait_until = None)
    32633:  Fetched https://www.atlassian.com/software/jira/update
    32634:  an unexpected error occurred while updating jira data
    32635:  Traceback (most recent call last):
    32636:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/jira.py", line 14, in <module>
    32637:  date = dates.parse_date(version_block.select_one('.releaselog').text)
    32638:  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    32639:  AttributeError: 'NoneType' object has no attribute 'text'
    32640:  Traceback (most recent call last):
    32641:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/jira.py", line 14, in <module>
    32642:  date = dates.parse_date(version_block.select_one('.releaselog').text)
    32643:  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    32644:  AttributeError: 'NoneType' object has no attribute 'text'
    32645:  The above exception was the direct cause of the following exception:
    32646:  Traceback (most recent call last):
    32647:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/jira.py", line 8, in <module>
    32648:  with releasedata.ProductData("jira") as product_data:
    32649:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 124, in __exit__
    32650:  raise ProductUpdateError(message) from exc_value
    32651:  common.releasedata.ProductUpdateError: an unexpected error occurred while updating jira data
    ...
    
    34670:  skipping release with name 2.8.x: does not contain releaseDate or releaseLogDate fields
    34671:  skipping release with name 2.9.x: does not contain releaseDate or releaseLogDate fields
    34672:  skipping release with name 2.10.x: does not contain releaseDate or releaseLogDate fields
    34673:  no update detected for kuma
    34674:  Traceback (most recent call last):
    34675:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/kuma.py", line 13, in <module>
    34676:  with releasedata.ProductData("kuma") as product_data:
    34677:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 129, in __exit__
    34678:  raise ProductUpdateError(message)
    34679:  common.releasedata.ProductUpdateError: no update detected for kuma
    ...
    
    50285:  Extended Support - TBD for oracle-database#23: field eol(patching end date)'s value 'Premier Support - December 31, 2031
    50286:  Extended Support - TBD' does not match any regex in [re.compile('^(?P<value>\\w+( \\d+,)? \\d+).*', re.MULTILINE)]
    50287:  adding release 21 to oracle-database
    50288:  set 'eol' in oracle-database#21 to 2027-07-31
    50289:  adding release 19 to oracle-database
    50290:  set 'eol' in oracle-database#19 to 2029-12-31
    50291:  adding release 18 to oracle-database
    50292:  set 'eol' in oracle-database#18 to 2021-06-30
    50293:  skipping row ['12.2.0.1', 'Mar 31, 2022 \nUpgrade Support (Restricted Availability) Jan 1, 2024- Dec 31, 2025 -\xa0Contact CSS for details', 'Error Correction / Patching has ended for this release.\n12.2.0.1 is not eligible for Extended Support (ES)\nUpgrade Support (Restricted Availability) (aka MDS) required to provision and/or run 12.2.0.1 on Exadata Database Service, Base Database Service or Exadata Cloud@Customer']: invalid release cycle '12.2.0.1', should match one of [re.compile('^(?P<value>\\d+)[a-z].*', re.MULTILINE)] and not match all of []
    50294:  skipping row ['12.1.0.2\nTerminal Release', 'Jul 31, 2022 with paid ES, ULA, or EBS waiver\nUpgrade Support\xa0(Restricted Availability) through Dec 31, 2025 - Contact CSS for details', 'Error Correction / Patching has ended for this release.\nPremier Support (PS) ended Jul 31, 2018 and one year of free Extended Support (ES) was in effect until July 31, 2019.\nES fees or a ULA was required beginning 01-Aug-2019 through 31-Jul-2022. Without paid ES or ULA, patching ended 31-Jul-2019.\nA global ES uplift fee waiver was in place for E-Business customers. For details and dates of expiration see: Extended Support Fee Waiver for Oracle Database 12.1 and 11.2 for Oracle E-Business Suite (Doc ID 2522948.1) or Technical Support Policy Document.\nApple Macintosh platform patching end date (Error Correction end date) was July 31, 2021. \nMicrosoft Windows: Regardless of the version used to run the 12.1.0.2 Database, Oracle built the 12.1.0.2 Database on Microsoft Windows 2008. This platform reached end-of-life support on January 14, 2020. Oracle made reasonable efforts to deliver patches for the Database 12.1.0.2 on Windows until July 2022 but that support has expired. \nUpgrade Support (Restricted Availability) (aka MDS) is required to provision and/or run 12.1.0.2 on Exadata Database Service, Base Database Service or Exadata Cloud@Customer']: invalid release cycle '12.1.0.2
    50295:  Terminal Release', should match one of [re.compile('^(?P<value>\\d+)[a-z].*', re.MULTILINE)] and not match all of []
    50296:  skipping row ['12.1.0.1', 'Aug 31, 2016', 'Error Correction / Patching has ended for this release.\n12.1.0.1 is not eligible for Extended Support (ES)\n12.1.0.1 was the last release of Standard Edition (SE) and Standard Edition One (SE1)']: invalid release cycle '12.1.0.1', should match one of [re.compile('^(?P<value>\\d+)[a-z].*', re.MULTILINE)] and not match all of []
    ...
    
    59140:  loaded data for rocket-chat from releases/rocket-chat.json
    59141:  Fetching ['https://docs.rocket.chat/docs/version-durability']
    59142:  Fetched ['https://docs.rocket.chat/docs/version-durability']
    59143:  no update detected for rocket-chat
    59144:  Traceback (most recent call last):
    59145:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/release_table.py", line 148, in <module>
    59146:  with releasedata.ProductData(config.product) as product_data:
    59147:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 129, in __exit__
    59148:  raise ProductUpdateError(message)
    59149:  common.releasedata.ProductUpdateError: no update detected for rocket-chat
    ...
    
    62754:  Fetched https://spring.io/projects/spring-boot#support
    62755:  processing table with headers ['branch', 'initial release', 'end of oss support', 'end enterprise support *']
    62756:  skipping table with headers ['branch', 'initial release', 'end of oss support', 'end enterprise support *']: 'end of support' is not in list
    62757:  no update detected for spring-boot
    62758:  Traceback (most recent call last):
    62759:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/release_table.py", line 148, in <module>
    62760:  with releasedata.ProductData(config.product) as product_data:
    62761:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 129, in __exit__
    62762:  raise ProductUpdateError(message)
    62763:  common.releasedata.ProductUpdateError: no update detected for spring-boot
    ...
    
    63025:  Fetched https://spring.io/projects/spring-framework#support
    63026:  processing table with headers ['branch', 'initial release', 'end of oss support', 'end enterprise support *']
    63027:  skipping table with headers ['branch', 'initial release', 'end of oss support', 'end enterprise support *']: 'end of support' is not in list
    63028:  no update detected for spring-framework
    63029:  Traceback (most recent call last):
    63030:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/release_table.py", line 148, in <module>
    63031:  with releasedata.ProductData(config.product) as product_data:
    63032:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 129, in __exit__
    63033:  raise ProductUpdateError(message)
    63034:  common.releasedata.ProductUpdateError: no update detected for spring-framework
    ...
    
    66946:  no data found for unrealircd at releases/unrealircd.json
    66947:  Fetching ['https://www.unrealircd.org/docwiki/index.php?title=History_of_UnrealIRCd_releases&action=raw']
    66948:  Fetched ['https://www.unrealircd.org/docwiki/index.php?title=History_of_UnrealIRCd_releases&action=raw']
    66949:  no update detected for unrealircd
    66950:  Traceback (most recent call last):
    66951:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/unrealircd.py", line 8, in <module>
    66952:  with releasedata.ProductData("unrealircd") as product_data:
    66953:  File "/home/runner/work/release-parser/release-parser/_data/releaselog/src/common/releasedata.py", line 129, in __exit__
    66954:  raise ProductUpdateError(message)
    66955:  common.releasedata.ProductUpdateError: no update detected for unrealircd
    ...
    
    70586:  adding version 3.3.2 (2010-11-12 06:45:21+00:00) to zookeeper
    70587:  adding version 3.3.1 (2010-05-07 17:15:35+00:00) to zookeeper
    70588:  adding version 3.3.0 (2010-03-19 18:39:04+00:00) to zookeeper
    70589:  updating releases/zookeeper.json data
    70590:  ran src/maven.py for zookeeper#maven(org.apache.zookeeper/zookeeper), took 0.44s (success=True)
    70591:  ##[endgroup]
    70592:  GITHUB_STEP_SUMMARY (exists=True):
    70593:  ## Script execution summary
    70594:  Executions below 3 seconds are hidden except in case of failure.
    ...
    
    70683:  | gke | 5.28s | 1 | ✅ |
    70684:  | artifactory | 4.57s | 1 | ✅ |
    70685:  | cos | 4.23s | 1 | ✅ |
    70686:  | oracle-jdk | 3.85s | 1 | ✅ |
    70687:  | rds | 3.69s | 3 | ✅ |
    70688:  | haproxy | 3.18s | 1 | ✅ |
    70689:  ## Update summary
    70690:  No update
    70691:  ##[error]Process completed with exit code 1.
    ...
    
    70695:  env:
    70696:  pythonLocation: /opt/hostedtoolcache/Python/3.11.10/x64
    70697:  PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.11.10/x64/lib/pkgconfig
    70698:  Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.10/x64
    70699:  Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.10/x64
    70700:  Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.10/x64
    70701:  LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.10/x64/lib
    70702:  ##[endgroup]
    70703:  ##[error]Process completed with exit code 1.
    

    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"
    

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    Signed-off-by: NxPKG <[email protected]>
    Copy link

    @coderabbitai coderabbitai bot left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Actionable comments posted: 1

    🧹 Outside diff range and nitpick comments (2)
    .github/workflows/update.yml (2)

    63-65: Add error handling for directory change and requirements.txt

    While the path change aligns with the new structure, we should add error handling to ensure the script fails gracefully if the directory or requirements.txt file doesn't exist.

    -        run: |
    -          cd _data/releaselog/
    -          pip install -r requirements.txt
    +        run: |
    +          cd _data/releaselog/ || exit 1
    +          if [ ! -f requirements.txt ]; then
    +            echo "Error: requirements.txt not found in _data/releaselog/"
    +            exit 1
    +          fi
    +          pip install -r requirements.txt

    72-74: Add logging and error handling for update script execution

    While the workflow is configured to continue on error, we should add better logging to help diagnose issues when they occur.

    -        run: |
    -          cd _data/releaselog/
    -          python update.py
    +        run: |
    +          echo "Starting update process..."
    +          cd _data/releaselog/ || {
    +            echo "Error: Failed to change to _data/releaselog/ directory"
    +            exit 1
    +          }
    +          if [ ! -f update.py ]; then
    +            echo "Error: update.py not found in _data/releaselog/"
    +            exit 1
    +          fi
    +          echo "Running update script..."
    +          python update.py
    +          echo "Update process completed"
    📜 Review details

    Configuration used: CodeRabbit UI
    Review profile: CHILL

    📥 Commits

    Reviewing files that changed from the base of the PR and between bff73c6 and 0527b86.

    📒 Files selected for processing (2)
    • .github/workflows/lint.yml (1 hunks)
    • .github/workflows/update.yml (2 hunks)
    🔇 Additional comments (3)
    .github/workflows/lint.yml (1)

    5-5: This change appears unrelated to the PR's objective of fixing site URLs.

    The branch name change from 'main' to 'master' seems to be outside the scope of this PR, which is primarily focused on updating site URLs.

    Let's verify the repository's default branch:

    .github/workflows/update.yml (2)

    Line range hint 45-74: Overall changes look good with minor suggestions

    The path structure changes are consistent with the PR objectives of fixing the site URL and align well with the changes in other files (_config.yml, README.md, and assets/openapi.yml). The workflow's core functionality remains intact while improving organization.

    While the changes themselves are correct, consider implementing the suggested error handling improvements to make the workflow more robust and easier to debug.


    45-45: Verify path consistency across the repository

    The repository path has been updated to _data/releaselog/website. While this change makes sense as part of the URL restructuring, we should ensure this new path is consistently used across all configurations and documentation.

    Also applies to: 53-53

    ✅ Verification successful

    Path structure is consistent with repository layout

    Based on the repository structure and workflow files analysis, the path _data/releaselog/website is correctly aligned with the repository's organization. The directory structure shows that _data/releaselog exists and is actively used, and the workflow file correctly references this path for the website repository checkout. No inconsistencies were found in the path usage across the configuration files.

    🏁 Scripts executed

    The following scripts were executed for the analysis:

    Script:

    #!/bin/bash
    # Description: Check for any references to the old path structure
    # and verify consistency of the new path
    
    # Search for any remaining references to the old 'website' path
    rg -i 'path:\s*website\b' --type yaml
    
    # Search for all references to the new path structure to ensure consistency
    rg -i '_data/releaselog/website' --type yaml
    

    Length of output: 84


    Script:

    #!/bin/bash
    # Let's try a broader search to understand the path structure and its usage
    
    # Find all YAML files in the repository
    echo "=== YAML files ==="
    fd -e yml -e yaml
    
    # Search for any path-related configurations in YAML files
    echo -e "\n=== Path configurations in YAML files ==="
    rg -i "path:" --type yaml -A 2 -B 2
    
    # Look for any references to releaselog or website directories
    echo -e "\n=== References to releaselog or website ==="
    rg -i "releaselog|website" --type yaml
    

    Length of output: 1000


    Script:

    #!/bin/bash
    # Let's check the entire repository structure and GitHub workflow files specifically
    
    # Show the directory structure focusing on _data and .github directories
    echo "=== Directory Structure ==="
    fd . _data .github
    
    # Check all GitHub workflow files content
    echo -e "\n=== GitHub Workflow Files Content ==="
    fd -e yml -e yaml . .github/workflows --exec cat {}
    

    Length of output: 21492

    @@ -2,7 +2,7 @@ name: Lint

    on:
    push:
    branches: ['main']
    branches: ['master']
    Copy link

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    🛠️ Refactor suggestion

    Consider keeping 'main' as the branch name.

    GitHub and the Git community have moved away from 'master' in favor of 'main' as the default branch name. Unless there's a specific reason for this change, it's recommended to stick with 'main' to align with modern Git practices.

    -    branches: ['master']
    +    branches: ['main']
    📝 Committable suggestion

    ‼️ IMPORTANT
    Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

    Suggested change
    branches: ['master']
    branches: ['main']

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants