chore: update versions

[flatfiledocker]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@flatfile/plugin-autocast@1.0.0

Minor Changes

• 2829595: This release adds support for the new string-list and enum-list field types.

Patch Changes

• Updated dependencies [2829595]
  • @flatfile/plugin-record-hook@1.6.0

@flatfile/plugin-constraints@2.0.0

Minor Changes

• 2829595: This release adds support for the new string-list and enum-list field types.

Patch Changes

• Updated dependencies [2829595]
  • @flatfile/plugin-record-hook@1.6.0

@flatfile/plugin-record-hook@1.6.0

Minor Changes

• 2829595: This release adds support for the new string-list and enum-list field types.

@flatfile/plugin-job-handler@0.5.3

Patch Changes

• cf24f9b: This release changes the jobHandler's starting progress from 10% to 1%

[coderabbitai]

Walkthrough

The recent updates across multiple plugins introduce support for new field types (string-list and enum-list) and include dependency updates. Specifically, @flatfile/plugin-autocast and @flatfile/plugin-constraints have added these new field types and updated their dependencies. Additionally, @flatfile/plugin-job-handler adjusts the starting progress of jobHandler from 10% to 1%, and @flatfile/plugin-record-hook now supports the new field types.

Changes

File Path	Change Summary
plugins/autocast/CHANGELOG.md	Added support for new field types (string-list and enum-list); updated dependencies.
plugins/constraints/CHANGELOG.md	Added support for new field types (string-list and enum-list); updated dependencies.
plugins/job-handler/CHANGELOG.md	Adjusted starting progress of jobHandler from 10% to 1%.
plugins/record-hook/CHANGELOG.md	Added support for new field types (string-list and enum-list).

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f4c70dd and d20c603.

Files ignored due to path filters (4)

• plugins/autocast/package.json is excluded by !**/*.json
• plugins/constraints/package.json is excluded by !**/*.json
• plugins/job-handler/package.json is excluded by !**/*.json
• plugins/record-hook/package.json is excluded by !**/*.json

Files selected for processing (4)

• plugins/autocast/CHANGELOG.md (1 hunks)
• plugins/constraints/CHANGELOG.md (1 hunks)
• plugins/job-handler/CHANGELOG.md (1 hunks)
• plugins/record-hook/CHANGELOG.md (1 hunks)

Additional Context Used

LanguageTool (9)

plugins/autocast/CHANGELOG.md (1)

Near line 91: Possible missing comma found.
Context: ...al. This also moves the listener dep to peerDependencies which are considered externals. - Updat...
Rule ID: AI_HYDRA_LEO_MISSING_COMMA

plugins/constraints/CHANGELOG.md (1)

Near line 62: Possible missing comma found.
Context: ...al. This also moves the listener dep to peerDependencies which are considered externals. - Updat...
Rule ID: AI_HYDRA_LEO_MISSING_COMMA

plugins/job-handler/CHANGELOG.md (4)

Near line 68: A comma may be missing after the conjunctive/linking adverb ‘Additionally’.
Context: ...and creates a bulk record deletion job. Additionally it improves error messaging and bundles...
Rule ID: SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA

---

Near line 68: The official spelling of this programming framework is “Node.js”.
Context: ...es error messaging and bundles for both NodeJS and the browser. `@flatfile/plugin-j...
Rule ID: NODE_JS

---

Near line 70: Loose punctuation mark.
Context: ...owser. @flatfile/plugin-job-handler: This release updates jobHandler's job...
Rule ID: UNLIKELY_OPENING_PUNCTUATION

---

Near line 72: Loose punctuation mark.
Context: ...EventFilter. @flatfile/util-common`: This release fixes cross compatibility ...
Rule ID: UNLIKELY_OPENING_PUNCTUATION

plugins/record-hook/CHANGELOG.md (3)

Near line 188: The singular proper name ‘Bug’ must be used with a third-person or a past tense verb.
Context: ...1.11 ### Patch Changes - 4d3fd49: Bug fix for record comparison ## 1.1.10 ### P...
Rule ID: HE_VERB_AGR

---

Near line 245: The singular proper name ‘Bug’ must be used with a third-person or a past tense verb.
Context: ....1.2 ### Patch Changes - b057912: Bug fix for bulkRecordhook caching ## 1.1.1 #...
Rule ID: HE_VERB_AGR

---

Near line 251: The singular proper name ‘Bug’ must be used with a third-person or a past tense verb.
Context: ....1.1 ### Patch Changes - 59a8b18: Bug fix to handle asynchronous handlers ## 1.1...
Rule ID: HE_VERB_AGR

Markdownlint (11)

plugins/job-handler/CHANGELOG.md (11)

104: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

117: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

127: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

140: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

150: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

158: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

169: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

177: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

185: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

193: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

---

202: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

Additional comments not posted (4)

plugins/constraints/CHANGELOG.md (1)

3-13: The changelog entries for version 2.0.0 are clear and accurately reflect the changes made in this version.

plugins/job-handler/CHANGELOG.md (1)

3-8: The changelog entries for version 0.5.3 are clear and accurately reflect the functional change made to the jobHandler's starting progress.

plugins/autocast/CHANGELOG.md (1)

3-13: The changelog entries for version 1.0.0 are clear and accurately reflect the changes made in this version.

plugins/record-hook/CHANGELOG.md (1)

3-8: The changelog entries for version 1.6.0 are clear and accurately reflect the addition of support for new field types.

---

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.
  • @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 as 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 full the 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.

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.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

plugins/job-handler/CHANGELOG.md (1)

Line range hint 104-202: Adjust heading levels to maintain a consistent structure.

- #### 2024-02-07
+ ### 2024-02-07
- #### 2024-02-05
+ ### 2024-02-05
- #### 2024-01-09
+ ### 2024-01-09
- #### 2023-12-18
+ ### 2023-12-18
- #### 2023-11-28
+ ### 2023-11-28
- #### 2023-11-09
+ ### 2023-11-09
- #### 2023-10-10
+ ### 2023-10-10
- #### 2023-09-27
+ ### 2023-09-27
- #### 2023-09-17
+ ### 2023-09-17
- #### 2023-09-08
+ ### 2023-09-08
- #### 2023-08-30
+ ### 2023-08-30

This change ensures that heading levels only increment by one level at a time, maintaining a consistent and accessible document structure.