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

Downgrade sqlite version while building executables #8435

Merged
merged 1 commit into from
May 9, 2024

Conversation

pranavxc
Copy link
Member

@pranavxc pranavxc commented May 9, 2024

Change Summary

Change type

  • feat: (new feature for the user, not a new feature for build script)
  • fix: (bug fix for the user, not a fix to a build script)
  • docs: (changes to the documentation)
  • style: (formatting, missing semi colons, etc; no production code change)
  • refactor: (refactoring production code, eg. renaming a variable)
  • test: (adding missing tests, refactoring tests; no production code change)
  • chore: (updating grunt tasks etc; no production code change)

Test/ Verification

Provide summary of changes.

Additional information / screenshots (optional)

Anything for maintainers to be made aware of

Signed-off-by: Pranav C <pranavxc@gmail.com>
Copy link
Contributor

coderabbitai bot commented May 9, 2024

Walkthrough

Walkthrough

The changes involve the addition of a script and a command in the GitHub workflow to specifically downgrade the sqlite3 package to version 5.1.6. This adjustment addresses a build failure issue with the latest version of sqlite3, which has dropped node-pre-gyp support, affecting executable builds.

Changes

File Path Change Summary
.github/workflows/release-executables.yml Added command to downgrade sqlite3 to version 5.1.6 before building executables.
scripts/downgradeSqlite.js Created script to modify package.json to ensure sqlite3 is set to version 5.1.6.

Assessment against linked issues

Objective Addressed Explanation
Executable build action fails when using latest version of sqlite3 package (#7860)

The changes made in the PR directly address the issue of executable build failures due to the incompatibility of the latest sqlite3 version with the existing build setup, by enforcing the use of an older, compatible version.


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

@pranavxc pranavxc marked this pull request as ready for review May 9, 2024 06:45
@pranavxc pranavxc requested a review from mertmit May 9, 2024 06:45
Copy link
Contributor

@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

Out of diff range and nitpick comments (2)
.github/workflows/release-executables.yml (2)

Line range hint 69-104: Security risk due to variable interpolation with github context data.

-          npm i -E nocodb@${{ github.event.inputs.tag || inputs.tag }}
+          npm i -E nocodb@"$TAG"
-          # Install nocodb version based on provided tag name
+          # Install nocodb version based on provided tag name, ensuring safe handling of user input

To mitigate potential security risks associated with code injection, replace direct interpolation of github context data with an environment variable that is properly sanitized and quoted. This change should be applied to all instances within this script block.


Line range hint 187-212: Security risk due to variable interpolation with github context data in Homebrew formula generation.

-          url "https://github.com/nocodb/nocodb/releases/download/${{ github.event.inputs.tag || inputs.tag }}/nocodb.tar.gz"
+          url "https://github.com/nocodb/nocodb/releases/download/$TAG/nocodb.tar.gz"
-          sha256 "${{ steps.compress.outputs.CHECKSUM }}"
+          sha256 "$CHECKSUM"
-          version "${{ github.event.inputs.tag || inputs.tag }}"
+          version "$TAG"

To prevent potential security risks from code injection, replace direct interpolation of github context data with environment variables that are properly sanitized and quoted. This change should be applied to all instances within this script block.

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 5be970b and 53d38c9.
Files selected for processing (2)
  • .github/workflows/release-executables.yml (1 hunks)
  • scripts/downgradeSqlite.js (1 hunks)
Files skipped from review due to trivial changes (1)
  • scripts/downgradeSqlite.js

@dstala dstala merged commit 0b79e45 into develop May 9, 2024
1 check passed
@dstala dstala deleted the chore/7860-executable-build-action branch May 9, 2024 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Executable build action fails when using latest version of sqlite3 package
3 participants