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

chore(release): pulling release/3.1.0 into main #1661

Merged
merged 15 commits into from
Mar 21, 2024
Merged

Conversation

devops-github-rudderstack
Copy link
Contributor

@devops-github-rudderstack devops-github-rudderstack commented Mar 21, 2024

👑 An automated PR

Summary by CodeRabbit

  • New Features
    • Enhanced GitHub Actions workflows for optimized deployment and notification procedures.
    • Upgraded package versions in analytics modules for improved functionality and dependency management.
  • Bug Fixes
    • Ensured consistent capitalization of "JavaScript" in multiple README.md files.
    • Enhanced reliability by updating URLs from beta to production versions in the analytics JS code.
  • Documentation
    • Updated CHANGELOG and README files in various packages for better version tracking and clarity on changes.
  • Chores
    • Adjusted the CODEOWNERS file to reflect updated ownership of a specific directory.
  • Refactor
    • Improved naming conventions in GitHub Actions workflows for clarity and consistency.

saikumarrs and others added 14 commits March 18, 2024 16:49
… test (#1654)

* chore: default constant for plugins and integrations base url updated

* chore: updated beta path in unit test
* feat: remove beta status for all the packages

* fix: mono repo version bump

* chore: remove beta status from package version

* chore: use user group for code owners

* chore: use github runner for publishing new releases

* chore: fix inconsistencies in github workflows

* fix: dependency chain across all the packages and typos

* fix: reset the crypto-es version

* fix: crypto-js, crypto-es and vulnerable versions

* chore: upgrade size-limit action to the latest version
Copy link
Contributor

coderabbitai bot commented Mar 21, 2024

Walkthrough

The updates focus on refining GitHub Actions workflows, enhancing documentation, and updating package versions across various components of a JavaScript SDK ecosystem. Key adjustments include transitioning to GitHub hosted runners, renaming steps for clarity, correcting "JavaScript" capitalization, and updating dependencies. These changes streamline CI/CD processes, improve readability, and ensure the SDK components are up-to-date, reflecting a commitment to maintaining a polished and efficient development pipeline.

Changes

Files Summary
.github/workflows/deploy-*.yml Updated configurations and step names for clarity in deployment workflows.
CODEOWNERS Updated directory ownership to @rudderlabs/js-sdk.
packages/*/CHANGELOG*.md Version updates and dependency changes in SDK packages.
packages/*/README.md Corrected "JavaScript" capitalization in SDK descriptions.
packages/analytics-js/__tests__/.../cdnPaths.test.ts Modified CDN path assertion in a test function.
packages/analytics-js/src/constants/urls.ts Updated URLs from beta to production versions.
sonar-project.properties Updated sonar.projectVersion to 3.1.0.

Poem

In the code forest, under the moon's bright gaze,
A diligent rabbit updates with grace. 🐰💻
"JavaScript," not "Javascript," it keenly notes,
As through GitHub Actions and workflows it floats.
With every change, it hops with delight,
For cleaner code makes the future bright. 🌟
"To better versions we leap," it cheers,
As it bounds forward, shedding outdated fears.

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-tests 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 tests 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 tests.
    • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

codecov bot commented Mar 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.89%. Comparing base (2d804a5) to head (ac550b3).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1661   +/-   ##
=======================================
  Coverage   53.89%   53.89%           
=======================================
  Files         461      461           
  Lines       15588    15588           
  Branches     3097     3105    +8     
=======================================
  Hits         8401     8401           
+ Misses       5881     5833   -48     
- Partials     1306     1354   +48     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 2d804a5 and 6118bac.
Files ignored due to path filters (19)
  • migrations.json is excluded by: !**/*.json
  • package-lock.json is excluded by: !**/*.json
  • package.json is excluded by: !**/*.json
  • packages/analytics-js-common/package.json is excluded by: !**/*.json
  • packages/analytics-js-common/project.json is excluded by: !**/*.json
  • packages/analytics-js-integrations/package.json is excluded by: !**/*.json
  • packages/analytics-js-integrations/project.json is excluded by: !**/*.json
  • packages/analytics-js-plugins/package.json is excluded by: !**/*.json
  • packages/analytics-js-plugins/project.json is excluded by: !**/*.json
  • packages/analytics-js-service-worker/package.json is excluded by: !**/*.json
  • packages/analytics-js-service-worker/project.json is excluded by: !**/*.json
  • packages/analytics-js/package.json is excluded by: !**/*.json
  • packages/analytics-js/project.json is excluded by: !**/*.json
  • packages/analytics-v1.1/package.json is excluded by: !**/*.json
  • packages/analytics-v1.1/project.json is excluded by: !**/*.json
  • packages/loading-scripts/package.json is excluded by: !**/*.json
  • packages/loading-scripts/project.json is excluded by: !**/*.json
  • packages/sanity-suite/package.json is excluded by: !**/*.json
  • packages/sanity-suite/project.json is excluded by: !**/*.json
Files selected for processing (31)
  • .github/workflows/deploy-npm.yml (2 hunks)
  • .github/workflows/deploy-prod.yml (6 hunks)
  • .github/workflows/deploy-staging.yml (1 hunks)
  • .github/workflows/publish-new-release.yml (1 hunks)
  • .github/workflows/security-code-quality-and-bundle-size-checks.yml (1 hunks)
  • CODEOWNERS (1 hunks)
  • packages/analytics-js-common/CHANGELOG.md (1 hunks)
  • packages/analytics-js-common/CHANGELOG_LATEST.md (1 hunks)
  • packages/analytics-js-common/README.md (1 hunks)
  • packages/analytics-js-integrations/CHANGELOG.md (1 hunks)
  • packages/analytics-js-integrations/CHANGELOG_LATEST.md (1 hunks)
  • packages/analytics-js-integrations/README.md (1 hunks)
  • packages/analytics-js-plugins/CHANGELOG.md (1 hunks)
  • packages/analytics-js-plugins/CHANGELOG_LATEST.md (1 hunks)
  • packages/analytics-js-plugins/README.md (1 hunks)
  • packages/analytics-js-service-worker/CHANGELOG.md (1 hunks)
  • packages/analytics-js-service-worker/CHANGELOG_LATEST.md (1 hunks)
  • packages/analytics-js-service-worker/README.md (1 hunks)
  • packages/analytics-js/CHANGELOG.md (1 hunks)
  • packages/analytics-js/CHANGELOG_LATEST.md (1 hunks)
  • packages/analytics-js/README.md (1 hunks)
  • packages/analytics-js/tests/components/configManager/cdnPaths.test.ts (1 hunks)
  • packages/analytics-js/src/constants/urls.ts (1 hunks)
  • packages/analytics-v1.1/CHANGELOG.md (1 hunks)
  • packages/analytics-v1.1/CHANGELOG_LATEST.md (1 hunks)
  • packages/loading-scripts/CHANGELOG.md (1 hunks)
  • packages/loading-scripts/CHANGELOG_LATEST.md (1 hunks)
  • packages/loading-scripts/README.md (1 hunks)
  • packages/sanity-suite/CHANGELOG.md (1 hunks)
  • packages/sanity-suite/README.md (1 hunks)
  • sonar-project.properties (1 hunks)
Files skipped from review due to trivial changes (19)
  • packages/analytics-js-common/README.md
  • packages/analytics-js-integrations/CHANGELOG.md
  • packages/analytics-js-integrations/README.md
  • packages/analytics-js-plugins/CHANGELOG.md
  • packages/analytics-js-plugins/CHANGELOG_LATEST.md
  • packages/analytics-js-plugins/README.md
  • packages/analytics-js-service-worker/CHANGELOG.md
  • packages/analytics-js-service-worker/CHANGELOG_LATEST.md
  • packages/analytics-js-service-worker/README.md
  • packages/analytics-js/CHANGELOG.md
  • packages/analytics-js/CHANGELOG_LATEST.md
  • packages/analytics-js/README.md
  • packages/analytics-v1.1/CHANGELOG.md
  • packages/loading-scripts/CHANGELOG.md
  • packages/loading-scripts/CHANGELOG_LATEST.md
  • packages/loading-scripts/README.md
  • packages/sanity-suite/CHANGELOG.md
  • packages/sanity-suite/README.md
  • sonar-project.properties
Additional comments: 20
CODEOWNERS (1)
  • 1-1: The update to the CODEOWNERS file looks good. Please ensure that @rudderlabs/js-sdk is an existing GitHub user or team with the appropriate permissions for the directory in question.
packages/analytics-js-common/CHANGELOG_LATEST.md (1)
  • 1-1: The version update in the CHANGELOG_LATEST.md for analytics-js-common is aligned with the PR objectives. Please ensure that the removal of features related to fetching an anonymous ID by cookie name and onboarding a new destination called ninetailed has been thoroughly discussed and agreed upon by the team.
packages/analytics-v1.1/CHANGELOG_LATEST.md (1)
  • 1-5: The dependency update for @rudderstack/analytics-js-common to version 2.48.3 in the CHANGELOG_LATEST.md for analytics-v1.1 is aligned with the PR objectives. Please ensure compatibility with this new version has been thoroughly tested.
packages/analytics-js-integrations/CHANGELOG_LATEST.md (1)
  • 1-5: The version update to 3.0.1 and the dependency update for @rudderstack/analytics-js-common to version 3.0.0 in the CHANGELOG_LATEST.md for analytics-js-integrations are aligned with the PR objectives. Please ensure compatibility with these updates has been thoroughly tested.
packages/analytics-js/src/constants/urls.ts (1)
  • 7-8: The update to production URLs in urls.ts is aligned with the PR objectives. Please ensure that these URLs are correct and accessible.
.github/workflows/security-code-quality-and-bundle-size-checks.yml (1)
  • 26-26: The update to version v2.10.0 of the github-action-check-size-limit action is aligned with the PR objectives. Please ensure that the workflow's functionality has been verified with this new version.
packages/analytics-js/__tests__/components/configManager/cdnPaths.test.ts (1)
  • 64-64: The modification to use the dummyVersion variable directly in the getIntegrationsCDNPath test assertion is a good improvement for maintainability. Please ensure that this change accurately reflects the intended behavior of the getIntegrationsCDNPath function.
.github/workflows/publish-new-release.yml (1)
  • 16-16: The update to use ubuntu-latest for the "Publish new release" job is aligned with the PR objectives. Please ensure that the workflow's functionality has been verified with this new runner environment.
.github/workflows/deploy-staging.yml (3)
  • 72-72: The change in the step name for syncing files to S3 staging directory improves clarity.
  • 80-80: The change in the step name for creating Cloudfront invalidation is clear and concise.
  • 85-85: The change in the step name for syncing files to S3 v1.1 staging directory is appropriate and enhances clarity.
.github/workflows/deploy-npm.yml (2)
  • 21-21: Switching to GitHub hosted runners for NPM package publishing is a good practice for security and reliability.
  • 75-75: The change in the step name for sending a message to the Slack channel is minor and acceptable.
packages/analytics-js-common/CHANGELOG.md (1)
  • 5-6: The version bump from 3.0.0-beta.19 to 3.0.1 is documented correctly, following semantic versioning principles.
.github/workflows/deploy-prod.yml (6)
  • 98-98: Renaming the step from "Sync files to S3 v3 folder" to "Sync files to S3" simplifies the step name and removes the version-specific reference, which could make the workflow more maintainable in the long term.
  • 110-110: Renaming the step to "Sync files to S3 versioned directory" clarifies the action being performed and aligns the terminology ("directory" instead of "folder"), which is more commonly used in the context of AWS S3.
  • 122-122: Updating the comment to refer to the '/latest' directory instead of '/latest' folder aligns with the consistent use of terminology across the workflow. It's also a good practice to note potential future changes in comments for maintainability.
  • 137-137: Renaming the step to "Send message to Slack channel" removes the version-specific reference, making it applicable for any future versions without needing to update the step name. This change contributes to the workflow's maintainability.
  • 172-172: Renaming the step to "Sync files to S3 v1.1 directory" improves clarity and aligns with the consistent terminology used throughout the workflow. It's important to maintain consistency in terminology for better readability and maintainability.
  • 187-187: The renaming of the step to "Sync files to S3 v1.1 versioned directory" not only aligns with the consistent use of terminology but also clarifies the action being performed. This change enhances the readability and maintainability of the workflow.

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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 6118bac and ac550b3.
Files selected for processing (1)
  • sonar-project.properties (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • sonar-project.properties

Copy link

github-actions bot commented Mar 21, 2024

size-limit report 📦

Name Size (Base) Size (Current) Size Limit Status
Common Code - No bundling 15.78 KB 15.81 KB (+0.19% ▲) 16.5 KB
Remote Module Federation Mapping - CDN 330 B 330 B (0%) 512 B
Remote Module Federated Plugins - CDN 5.71 KB 5.71 KB (0%) 6 KB
Core ESM - NPM 7.64 KB 7.64 KB (-0.02% ▼) 8 KB
Core CJS - NPM 22.43 KB 22.47 KB (+0.15% ▲) 23 KB
Core - NPM 22.6 KB 22.53 KB (-0.33% ▼) 23 KB
Core Legacy - CDN 42.88 KB 42.83 KB (-0.12% ▼) 44 KB
Core - CDN 22.7 KB 22.69 KB (-0.05% ▼) 23 KB
Core (legacy build) - CDN - v1.1 31.54 KB 31.45 KB (-0.27% ▼) 32 KB
Core - NPM - v1.1 31.52 KB 31.5 KB (-0.09% ▼) 32 KB
Service Worker Module 22.64 KB 22.64 KB (0%) 24 KB
All Integrations (legacy build) - CDN 98.57 KB 98.57 KB (0%) 105 KB

Copy link

sonarcloud bot commented Mar 21, 2024

@saikumarrs saikumarrs merged commit 60f2027 into main Mar 21, 2024
12 checks passed
@saikumarrs saikumarrs deleted the release/3.1.0 branch March 21, 2024 09:56
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.

4 participants