chore(release): pull main into develop post release v1.100.0 duplicate

[krishna2020]

What are the changes introduced in this PR?

Due to some manual errors in following release process, hotfix release through main & regular release through develop had same version 1.100.0 tagged.

What is the related Linear task?

Resolves INT-XXX

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

Any new checks got introduced or modified in test suites. Please explain the changes.

N/A

---

Developer checklist

• My code follows the style guidelines of this project

• No breaking changes are being introduced.

• All related docs linked with the PR?

• All changes manually tested?

• Any documentation changes needed with this change?

• I have executed schemaGenerator tests and updated schema if needed

• Are sensitive fields marked as secret in definition config?

• My test cases and placeholders use only masked/sample values for sensitive fields

• Is the PR limited to 10 file changes & one task?

Reviewer checklist

• Is the type of change in the PR title appropriate as per the changes?

• Verified that there are no credentials or confidential data exposed with the changes.

Summary by CodeRabbit

• New Features

  • Added tags for SDK source types in version 1.100.0

• Bug Fixes

  • Corrected display name casing for JavaScript source configuration

• Documentation

  • Updated CHANGELOG.md with version 1.100.0 details

[coderabbitai]

Walkthrough

The pull request introduces version [1.100.0] with a new feature for SDK source type tags and several bug fixes. The changelog documents the addition of this feature linked to issue #1841. A minor correction was also made to the display name of the JavaScript source configuration, updating the casing from "Javascript" to "JavaScript".

Changes

File	Change Summary
CHANGELOG.md	Updated to version [1.100.0], added feature for SDK source type tags, referenced bug fixes
src/configurations/sources/javascript/db-config.json	Corrected display name casing from "Javascript" to "JavaScript"

Poem

🐰 A rabbit's tale of code so bright,
Where 'Javascript' now stands upright!
SDK tags dancing with glee,
Version [1.100.0], set code free!
Precision in every byte and line,
Hopping forward, looking fine! 🚀

---

📜 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 e35a61c and 2995574.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• src/configurations/sources/javascript/db-config.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/configurations/sources/javascript/db-config.json

🔇 Additional comments (2)

CHANGELOG.md (2)

10-17: LGTM! Changelog entry format is correct

The changelog entry follows the conventional format with:

• Proper version number and date
• Categorized sections (Features/Bug Fixes)
• Links to issues and commits
• Clear descriptions of changes

---

10-11: Verify the version number duplication

The changelog shows version 1.100.0 being added, but according to the PR objectives, this version number was already used in both a hotfix release and a regular release. This needs to be resolved to avoid version number conflicts.

Run the following script to check for duplicate version tags:

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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