🔖 new release #628
🔖 new release #628
Conversation
PR SummaryPublishes
Written by Cursor Bugbot for commit 9c7410b. This will update automatically on new commits. Configure here. |
WalkthroughRemoved many .changeset files, bumped versions for root, server, common, and substreams packages, updated several package devDependency references across docs and .maestro, and added/updated CHANGELOG entries for substreams, common, server, and root packages. Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 1 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (30)
💤 Files with no reviewable changes (20)
🧰 Additional context used📓 Path-based instructions (2)**/*.md📄 CodeRabbit inference engine (.cursor/rules/markdown.mdc)
Files:
**/*.{mdc,md}📄 CodeRabbit inference engine (.cursor/rules/style.mdc)
Files:
🧠 Learnings (19)📚 Learning: 2025-12-23T19:56:56.405ZApplied to files:
📚 Learning: 2025-12-30T15:03:28.449ZApplied to files:
📚 Learning: 2025-12-30T15:03:28.449ZApplied to files:
📚 Learning: 2025-12-30T15:03:28.449ZApplied to files:
📚 Learning: 2025-12-23T19:58:16.574ZApplied to files:
📚 Learning: 2025-12-23T19:57:22.339ZApplied to files:
📚 Learning: 2025-12-23T19:57:22.339ZApplied to files:
📚 Learning: 2025-12-30T15:03:28.449ZApplied to files:
📚 Learning: 2025-12-30T15:03:28.449ZApplied to files:
📚 Learning: 2025-12-30T15:03:28.449ZApplied to files:
📚 Learning: 2025-12-23T19:57:22.339ZApplied to files:
📚 Learning: 2025-12-23T19:57:22.339ZApplied to files:
📚 Learning: 2026-01-08T19:54:15.788ZApplied to files:
📚 Learning: 2025-12-23T19:56:56.405ZApplied to files:
📚 Learning: 2026-01-05T21:07:40.716ZApplied to files:
📚 Learning: 2026-01-09T16:24:21.227ZApplied to files:
📚 Learning: 2025-12-23T19:57:07.685ZApplied to files:
📚 Learning: 2025-12-23T19:57:07.685ZApplied to files:
📚 Learning: 2025-12-23T19:58:16.574ZApplied to files:
🪛 LanguageToolcommon/CHANGELOG.md[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations. (DASH_RULE) substreams/CHANGELOG.md[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations. (DASH_RULE) [typographical] ~9-~9: Consider using an em dash in dialogues and enumerations. (DASH_RULE) [typographical] ~11-~11: Consider using an em dash in dialogues and enumerations. (DASH_RULE) [style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 917 characters long) (EN_EXCESSIVE_EXCLAMATION) [typographical] ~13-~13: Consider using an em dash in dialogues and enumerations. (DASH_RULE) 🔇 Additional comments (9)
✏️ Tip: You can disable this entire section by setting Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary of ChangesHello @cruzdanilo, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request represents an automated release for the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request, generated by the Changesets release action, prepares a new minor release for the @exactly/substreams package, version 0.1.0. The changes include version bumps in package.json for both the substreams and server packages, the generation of a CHANGELOG.md file, and the removal of the consumed changeset files. All changes are consistent with an automated release process and appear correct. I have no further comments.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #628 +/- ##
==========================================
- Coverage 79.27% 79.12% -0.16%
==========================================
Files 47 47
Lines 1969 1969
Branches 434 434
==========================================
- Hits 1561 1558 -3
- Misses 255 259 +4
+ Partials 153 152 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In @substreams/CHANGELOG.md:
- Line 5: Change the markdown heading text "Minor Changes" to use lowercase per
the docs guideline; update the heading string "Minor Changes" to "minor changes"
so all narrative text in internal documentation prose follows the lowercase
rule.
- Around line 7-13: Changelog lines for PR #627 (commit hashes 8dd17fd, 3c75c10,
2d4e0e7, 4720f68) exceed the 120-character limit; reflow each entry so no line
is longer than 120 chars (e.g., wrap after the PR/commit link or before the
description, splitting long descriptions into a second line), ensure "Thanks
@cruzdanilo!" follows lowercase prose (change "Thanks" → "thanks"), and apply
the same wrapping pattern to all four entries so each wrapped line stays within
the limit.
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (7)
.changeset/breezy-planes-repeat.md.changeset/rare-readers-tell.md.changeset/red-toys-pump.md.changeset/violet-poems-heal.mdserver/package.jsonsubstreams/CHANGELOG.mdsubstreams/package.json
💤 Files with no reviewable changes (4)
- .changeset/red-toys-pump.md
- .changeset/violet-poems-heal.md
- .changeset/breezy-planes-repeat.md
- .changeset/rare-readers-tell.md
🧰 Additional context used
📓 Path-based instructions (2)
**/*.md
📄 CodeRabbit inference engine (.cursor/rules/markdown.mdc)
**/*.md: Each markdown file must start with a single top-level heading (# heading 1)
Headings must be sequential (e.g.,#->##->###), do not skip levels
Do not end headings with punctuation (.,:,!,?)
Use a hyphen (-) for unordered list items in markdown
Sub-lists in markdown must be indented with a two-space offset
Always use unordered lists (-) instead of numbered lists (1.) in markdown
All code blocks must be fenced with backticks (```) and specify a language identifier
Useshor `bash` as the language identifier for shell commands in markdown code blocks
All code identifiers inside backticks or code fences must strictly follow casing rules defined in `style.mdc` (`camelCase` for variables, `PascalCase` for types, etc.)
All code comments must be lowercase
All lines in markdown files must be no longer than 120 characters
Surround all block-level elements (headings, lists, code blocks) with a single blank line in markdown
Do not add multiple consecutive blank lines in markdown files
No lines should have trailing whitespace in markdown files
Use asterisks (`word`) for italics and double asterisks (`word`) for bold in markdown
Provide descriptive titles for links in markdown instead of generic phrases like 'click here'Use proper sentence case for user-facing documentation in the
docs/directory
Files:
substreams/CHANGELOG.md
**/*.{mdc,md}
📄 CodeRabbit inference engine (.cursor/rules/style.mdc)
**/*.{mdc,md}: All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose
Files:
substreams/CHANGELOG.md
🪛 LanguageTool
substreams/CHANGELOG.md
[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa accounts - [#627](https://gi...
(DASH_RULE)
[typographical] ~9-~9: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ store exa accounts - [#627](https://...
(DASH_RULE)
[typographical] ~11-~11: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa plugins - [#627](https://git...
(DASH_RULE)
[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 917 characters long)
Context: ...uzdanilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(EN_EXCESSIVE_EXCLAMATION)
[typographical] ~13-~13: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(DASH_RULE)
⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: test
🔇 Additional comments (2)
substreams/package.json (1)
3-3: LGTM! Version bump aligns with the release.The version bump to 0.1.0 correctly reflects the minor changes documented in the changelog.
server/package.json (1)
64-64: LGTM! Dependency version aligned with substreams release.The devDependency update correctly references the new substreams package version.
cruzdanilo
force-pushed
the
changeset-release/main
branch
from
7262dd2 to
6d1df9c
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In @substreams/CHANGELOG.md:
- Line 5: Change the heading "### Minor Changes" to all lowercase to comply with
internal documentation prose rules; update the heading in the file where "###
Minor Changes" appears (e.g., the CHANGLEOG/section heading) to "### minor
changes" so the narrative text follows the lowercase guideline.
- Around line 7-13: Changelog lines with entries like "[#627] [`8dd17fd`]" (and
hashes `3c75c10`, `2d4e0e7`, `4720f68`) exceed 120 chars because of full inline
GitHub URLs; convert these inline links to reference-style links or move the
URLs to a references block at the bottom of substreams/CHANGELOG.md and keep the
visible lines as "[#627] [`8dd17fd`] Thanks [@cruzdanilo]! - ✨ map exa accounts"
(or wrap the description after the dash) so each visible line is <=120 chars,
then add the corresponding reference definitions (e.g. [#627]: <full PR URL> and
[`8dd17fd`]: <commit URL>) after the entries.
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (7)
.changeset/breezy-planes-repeat.md.changeset/rare-readers-tell.md.changeset/red-toys-pump.md.changeset/violet-poems-heal.mdserver/package.jsonsubstreams/CHANGELOG.mdsubstreams/package.json
💤 Files with no reviewable changes (4)
- .changeset/violet-poems-heal.md
- .changeset/rare-readers-tell.md
- .changeset/breezy-planes-repeat.md
- .changeset/red-toys-pump.md
🧰 Additional context used
📓 Path-based instructions (2)
**/*.md
📄 CodeRabbit inference engine (.cursor/rules/markdown.mdc)
**/*.md: Each markdown file must start with a single top-level heading (# heading 1)
Headings must be sequential (e.g.,#->##->###), do not skip levels
Do not end headings with punctuation (.,:,!,?)
Use a hyphen (-) for unordered list items in markdown
Sub-lists in markdown must be indented with a two-space offset
Always use unordered lists (-) instead of numbered lists (1.) in markdown
All code blocks must be fenced with backticks (```) and specify a language identifier
Useshor `bash` as the language identifier for shell commands in markdown code blocks
All code identifiers inside backticks or code fences must strictly follow casing rules defined in `style.mdc` (`camelCase` for variables, `PascalCase` for types, etc.)
All code comments must be lowercase
All lines in markdown files must be no longer than 120 characters
Surround all block-level elements (headings, lists, code blocks) with a single blank line in markdown
Do not add multiple consecutive blank lines in markdown files
No lines should have trailing whitespace in markdown files
Use asterisks (`word`) for italics and double asterisks (`word`) for bold in markdown
Provide descriptive titles for links in markdown instead of generic phrases like 'click here'Use proper sentence case for user-facing documentation in the
docs/directory
Files:
substreams/CHANGELOG.md
**/*.{mdc,md}
📄 CodeRabbit inference engine (.cursor/rules/style.mdc)
**/*.{mdc,md}: All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose
Files:
substreams/CHANGELOG.md
🧠 Learnings (12)
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: When implementing changes, follow all rules in `.mdc` files for any code, documentation, or rules you create, including meta-rules like the lowercase prose convention
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/.changeset/*.md : Use a lowercase sentence in the imperative present tense for changeset summaries
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to docs/**/*.md : Use proper sentence case for all user-facing documentation in `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:58:16.574Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-23T19:58:16.574Z
Learning: All internal documentation and commit messages must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All code comments must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{ts,tsx,js,jsx} : All code comments must be lowercase; special tags (TODO, FIXME) are uppercase followed by a single space and lowercase comment, without colons or dashes, and should include a ticket/issue reference when available
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.md : Use proper sentence case for user-facing documentation in the `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All code identifiers inside backticks or code fences must strictly follow casing rules defined in `style.mdc` (`camelCase` for variables, `PascalCase` for types, etc.)
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All lines in markdown files must be no longer than 120 characters
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2026-01-08T19:45:38.852Z
Learnt from: cruzdanilo
Repo: exactly/exa PR: 627
File: .github/workflows/substreams-build.yaml:2-2
Timestamp: 2026-01-08T19:45:38.852Z
Learning: In the exactly/exa repository, prefer concise inline YAML syntax (e.g., `on: { push: { tags: ["pattern"] }, workflow_dispatch: {} }`) over expanded multi-line format in GitHub workflow files, even if it triggers YAMLlint warnings about formatting.
Applied to files:
substreams/CHANGELOG.md
🪛 LanguageTool
substreams/CHANGELOG.md
[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa accounts - [#627](https://gi...
(DASH_RULE)
[typographical] ~9-~9: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ store exa accounts - [#627](https://...
(DASH_RULE)
[typographical] ~11-~11: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa plugins - [#627](https://git...
(DASH_RULE)
[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 917 characters long)
Context: ...uzdanilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(EN_EXCESSIVE_EXCLAMATION)
[typographical] ~13-~13: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(DASH_RULE)
🔇 Additional comments (2)
substreams/package.json (1)
3-3: LGTM! Version bump is correct.The minor version bump from 0.0.1 to 0.1.0 correctly reflects the addition of new features described in the changelog.
server/package.json (1)
64-64: LGTM! Dependency version correctly synchronized.The devDependency update aligns with the substreams package version bump.
cruzdanilo
force-pushed
the
changeset-release/main
branch
from
6d1df9c to
cbffa45
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @substreams/CHANGELOG.md:
- Around line 7-13: Wrap each changelog entry so no single line exceeds 120
characters: split the four entries that reference PR #627 and commits `8dd17fd`,
`3c75c10`, `2d4e0e7`, and `4720f68` into multiple lines (e.g., keep the PR link
and commit hash on the first line and place the author and the descriptive text
on subsequent wrapped lines), ensuring links remain intact and each wrapped line
is ≤120 characters.
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (7)
.changeset/breezy-planes-repeat.md.changeset/rare-readers-tell.md.changeset/red-toys-pump.md.changeset/violet-poems-heal.mdserver/package.jsonsubstreams/CHANGELOG.mdsubstreams/package.json
💤 Files with no reviewable changes (4)
- .changeset/violet-poems-heal.md
- .changeset/red-toys-pump.md
- .changeset/rare-readers-tell.md
- .changeset/breezy-planes-repeat.md
🧰 Additional context used
📓 Path-based instructions (2)
**/*.md
📄 CodeRabbit inference engine (.cursor/rules/markdown.mdc)
**/*.md: Each markdown file must start with a single top-level heading (# heading 1)
Headings must be sequential (e.g.,#->##->###), do not skip levels
Do not end headings with punctuation (.,:,!,?)
Use a hyphen (-) for unordered list items in markdown
Sub-lists in markdown must be indented with a two-space offset
Always use unordered lists (-) instead of numbered lists (1.) in markdown
All code blocks must be fenced with backticks (```) and specify a language identifier
Useshor `bash` as the language identifier for shell commands in markdown code blocks
All code identifiers inside backticks or code fences must strictly follow casing rules defined in `style.mdc` (`camelCase` for variables, `PascalCase` for types, etc.)
All code comments must be lowercase
All lines in markdown files must be no longer than 120 characters
Surround all block-level elements (headings, lists, code blocks) with a single blank line in markdown
Do not add multiple consecutive blank lines in markdown files
No lines should have trailing whitespace in markdown files
Use asterisks (`word`) for italics and double asterisks (`word`) for bold in markdown
Provide descriptive titles for links in markdown instead of generic phrases like 'click here'Use proper sentence case for user-facing documentation in the
docs/directory
Files:
substreams/CHANGELOG.md
**/*.{mdc,md}
📄 CodeRabbit inference engine (.cursor/rules/style.mdc)
**/*.{mdc,md}: All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose
Files:
substreams/CHANGELOG.md
🧠 Learnings (12)
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/.changeset/*.md : Use a lowercase sentence in the imperative present tense for changeset summaries
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: When implementing changes, follow all rules in `.mdc` files for any code, documentation, or rules you create, including meta-rules like the lowercase prose convention
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:58:16.574Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-23T19:58:16.574Z
Learning: All internal documentation and commit messages must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to docs/**/*.md : Use proper sentence case for all user-facing documentation in `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.md : Use proper sentence case for user-facing documentation in the `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All code comments must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{ts,tsx,js,jsx} : All code comments must be lowercase; special tags (TODO, FIXME) are uppercase followed by a single space and lowercase comment, without colons or dashes, and should include a ticket/issue reference when available
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All lines in markdown files must be no longer than 120 characters
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2026-01-09T16:24:11.460Z
Learnt from: cruzdanilo
Repo: exactly/exa PR: 627
File: .changeset/breezy-planes-repeat.md:5-5
Timestamp: 2026-01-09T16:24:11.460Z
Learning: In the exactly/exa repository, changeset summaries in .changeset/*.md files must include the gitmoji and follow the format `<emoji> <message>` (without the scope), matching the commit message format `<emoji> <scope>: <message>` but omitting the `<scope>:` portion.
Applied to files:
substreams/CHANGELOG.md
🪛 LanguageTool
substreams/CHANGELOG.md
[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa accounts - [#627](https://gi...
(DASH_RULE)
[typographical] ~9-~9: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ store exa accounts - [#627](https://...
(DASH_RULE)
[typographical] ~11-~11: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa plugins - [#627](https://git...
(DASH_RULE)
[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 917 characters long)
Context: ...uzdanilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(EN_EXCESSIVE_EXCLAMATION)
[typographical] ~13-~13: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(DASH_RULE)
🔇 Additional comments (2)
substreams/package.json (1)
3-3: LGTM! Version bump is correct.The minor version bump from 0.0.1 to 0.1.0 aligns with the PR objective and the changes documented in the changelog.
server/package.json (1)
64-64: LGTM! Dependency version aligned.The devDependency update correctly references the new 0.1.0 version of @exactly/substreams.
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In @substreams/CHANGELOG.md:
- Line 5: Change the Markdown heading "### Minor Changes" to all lowercase ("###
minor changes") so the narrative prose follows the internal documentation
guideline; locate the heading text in CHANGELOG.md and update the exact header
token to the lowercase variant.
- Around line 7-13: The changelog lines for PR #627 (commit hashes 8dd17fd,
3c75c10, 2d4e0e7, 4720f68) exceed the 120-character limit due to long inline
URLs; fix by breaking each entry into multiple shorter lines or converting the
inline links to reference-style links (move the long URLs to link definitions at
the bottom and replace inline URLs with [label] references) so every physical
line in CHANGELOG.md is <=120 characters while preserving the PR/commit and
author text.
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (7)
.changeset/breezy-planes-repeat.md.changeset/rare-readers-tell.md.changeset/red-toys-pump.md.changeset/violet-poems-heal.mdserver/package.jsonsubstreams/CHANGELOG.mdsubstreams/package.json
💤 Files with no reviewable changes (4)
- .changeset/rare-readers-tell.md
- .changeset/red-toys-pump.md
- .changeset/violet-poems-heal.md
- .changeset/breezy-planes-repeat.md
🧰 Additional context used
📓 Path-based instructions (2)
**/*.md
📄 CodeRabbit inference engine (.cursor/rules/markdown.mdc)
**/*.md: Each markdown file must start with a single top-level heading (# heading 1)
Headings must be sequential (e.g.,#->##->###), do not skip levels
Do not end headings with punctuation (.,:,!,?)
Use a hyphen (-) for unordered list items in markdown
Sub-lists in markdown must be indented with a two-space offset
Always use unordered lists (-) instead of numbered lists (1.) in markdown
All code blocks must be fenced with backticks (```) and specify a language identifier
Useshor `bash` as the language identifier for shell commands in markdown code blocks
All code identifiers inside backticks or code fences must strictly follow casing rules defined in `style.mdc` (`camelCase` for variables, `PascalCase` for types, etc.)
All code comments must be lowercase
All lines in markdown files must be no longer than 120 characters
Surround all block-level elements (headings, lists, code blocks) with a single blank line in markdown
Do not add multiple consecutive blank lines in markdown files
No lines should have trailing whitespace in markdown files
Use asterisks (`word`) for italics and double asterisks (`word`) for bold in markdown
Provide descriptive titles for links in markdown instead of generic phrases like 'click here'Use proper sentence case for user-facing documentation in the
docs/directory
Files:
substreams/CHANGELOG.md
**/*.{mdc,md}
📄 CodeRabbit inference engine (.cursor/rules/style.mdc)
**/*.{mdc,md}: All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose
Files:
substreams/CHANGELOG.md
🧠 Learnings (12)
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/.changeset/*.md : Use a lowercase sentence in the imperative present tense for changeset summaries
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: When implementing changes, follow all rules in `.mdc` files for any code, documentation, or rules you create, including meta-rules like the lowercase prose convention
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:58:16.574Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-23T19:58:16.574Z
Learning: All internal documentation and commit messages must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to docs/**/*.md : Use proper sentence case for all user-facing documentation in `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.md : Use proper sentence case for user-facing documentation in the `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All code comments must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{ts,tsx,js,jsx} : All code comments must be lowercase; special tags (TODO, FIXME) are uppercase followed by a single space and lowercase comment, without colons or dashes, and should include a ticket/issue reference when available
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All lines in markdown files must be no longer than 120 characters
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2026-01-09T16:24:11.460Z
Learnt from: cruzdanilo
Repo: exactly/exa PR: 627
File: .changeset/breezy-planes-repeat.md:5-5
Timestamp: 2026-01-09T16:24:11.460Z
Learning: In the exactly/exa repository, changeset summaries in .changeset/*.md files must include the gitmoji and follow the format `<emoji> <message>` (without the scope), matching the commit message format `<emoji> <scope>: <message>` but omitting the `<scope>:` portion.
Applied to files:
substreams/CHANGELOG.md
🪛 LanguageTool
substreams/CHANGELOG.md
[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa accounts - [#627](https://gi...
(DASH_RULE)
[typographical] ~9-~9: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ store exa accounts - [#627](https://...
(DASH_RULE)
[typographical] ~11-~11: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa plugins - [#627](https://git...
(DASH_RULE)
[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 917 characters long)
Context: ...uzdanilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(EN_EXCESSIVE_EXCLAMATION)
[typographical] ~13-~13: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(DASH_RULE)
🔇 Additional comments (2)
substreams/package.json (1)
3-3: LGTM!The version bump from 0.0.1 to 0.1.0 is appropriate for a minor release adding new features (map/store exa accounts, map/insert exa plugins).
server/package.json (1)
64-64: LGTM!The devDependency update correctly tracks the @exactly/substreams version bump from 0.0.1 to 0.1.0, maintaining consistency across the monorepo.
|
|
||
| ## 0.1.0 | ||
|
|
||
| ### Minor Changes |
There was a problem hiding this comment.
Use lowercase for heading text per coding guidelines.
The coding guidelines specify that all narrative text in internal documentation prose, including headings, must be lowercase. This heading should be ### minor changes.
Proposed fix
-### Minor Changes
+### minor changesBased on learnings, all prose in internal markdown files must be lowercase.
📝 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.
| ### Minor Changes | |
| ### minor changes |
🤖 Prompt for AI Agents
In @substreams/CHANGELOG.md at line 5, Change the Markdown heading "### Minor
Changes" to all lowercase ("### minor changes") so the narrative prose follows
the internal documentation guideline; locate the heading text in CHANGELOG.md
and update the exact header token to the lowercase variant.
cbffa45 to
9c7410b
Compare
![sentry[bot]](https://avatars.githubusercontent.com/u/1396951?s=60&v=4){kind=small}
| @@ -1,6 +1,6 @@ | |||
| { | |||
| "name": "@exactly/substreams", | |||
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
cruzdanilo
force-pushed
the
changeset-release/main
branch
from
9c7410b to
56d496b
Compare
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on February 2. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
cruzdanilo
force-pushed
the
changeset-release/main
branch
from
56d496b to
a9973dc
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In @CHANGELOG.md:
- Around line 7-10: CHANGELOG.md contains lines exceeding the 120-character
limit (notably the combined PR/commit/author entry and the dependency line on
lines 7, 9 and 10); fix by wrapping those long changelog entries so no single
line exceeds 120 characters—e.g., split the PR/commit/author entry into multiple
lines (PR link and commit link on one line, description/author on the next) and
break the dependency list items across lines, or alternatively update the
changeset generation config to emit wrapped entries or record an exception to
the line-length rule for autogenerated changelog lines.
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (9)
.changeset/breezy-planes-repeat.md.changeset/rare-readers-tell.md.changeset/red-toys-pump.md.changeset/violet-poems-heal.mdCHANGELOG.mdpackage.jsonserver/package.jsonsubstreams/CHANGELOG.mdsubstreams/package.json
💤 Files with no reviewable changes (4)
- .changeset/violet-poems-heal.md
- .changeset/red-toys-pump.md
- .changeset/rare-readers-tell.md
- .changeset/breezy-planes-repeat.md
🧰 Additional context used
📓 Path-based instructions (2)
**/*.md
📄 CodeRabbit inference engine (.cursor/rules/markdown.mdc)
**/*.md: Each markdown file must start with a single top-level heading (# heading 1)
Headings must be sequential (e.g.,#->##->###), do not skip levels
Do not end headings with punctuation (.,:,!,?)
Use a hyphen (-) for unordered list items in markdown
Sub-lists in markdown must be indented with a two-space offset
Always use unordered lists (-) instead of numbered lists (1.) in markdown
All code blocks must be fenced with backticks (```) and specify a language identifier
Useshor `bash` as the language identifier for shell commands in markdown code blocks
All code identifiers inside backticks or code fences must strictly follow casing rules defined in `style.mdc` (`camelCase` for variables, `PascalCase` for types, etc.)
All code comments must be lowercase
All lines in markdown files must be no longer than 120 characters
Surround all block-level elements (headings, lists, code blocks) with a single blank line in markdown
Do not add multiple consecutive blank lines in markdown files
No lines should have trailing whitespace in markdown files
Use asterisks (`word`) for italics and double asterisks (`word`) for bold in markdown
Provide descriptive titles for links in markdown instead of generic phrases like 'click here'Use proper sentence case for user-facing documentation in the
docs/directory
Files:
substreams/CHANGELOG.mdCHANGELOG.md
**/*.{mdc,md}
📄 CodeRabbit inference engine (.cursor/rules/style.mdc)
**/*.{mdc,md}: All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose
Files:
substreams/CHANGELOG.mdCHANGELOG.md
🧠 Learnings (15)
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All lines in markdown files must be no longer than 120 characters
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2026-01-08T19:45:38.852Z
Learnt from: cruzdanilo
Repo: exactly/exa PR: 627
File: .github/workflows/substreams-build.yaml:2-2
Timestamp: 2026-01-08T19:45:38.852Z
Learning: In the exactly/exa repository, prefer concise inline YAML syntax (e.g., `on: { push: { tags: ["pattern"] }, workflow_dispatch: {} }`) over expanded multi-line format in GitHub workflow files, even if it triggers YAMLlint warnings about formatting.
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2026-01-09T16:24:11.460Z
Learnt from: cruzdanilo
Repo: exactly/exa PR: 627
File: .changeset/breezy-planes-repeat.md:5-5
Timestamp: 2026-01-09T16:24:11.460Z
Learning: In the exactly/exa repository, changeset summaries in .changeset/*.md files must include the gitmoji and follow the format `<emoji> <message>` (without the scope), matching the commit message format `<emoji> <scope>: <message>` but omitting the `<scope>:` portion.
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/.changeset/*.md : Use a lowercase sentence in the imperative present tense for changeset summaries
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: When implementing changes, follow all rules in `.mdc` files for any code, documentation, or rules you create, including meta-rules like the lowercase prose convention
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:58:16.574Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-23T19:58:16.574Z
Learning: All internal documentation and commit messages must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All code comments must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to docs/**/*.md : Use proper sentence case for all user-facing documentation in `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{ts,tsx,js,jsx} : All code comments must be lowercase; special tags (TODO, FIXME) are uppercase followed by a single space and lowercase comment, without colons or dashes, and should include a ticket/issue reference when available
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.md : Use proper sentence case for user-facing documentation in the `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:56:56.405Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/dev.mdc:0-0
Timestamp: 2025-12-23T19:56:56.405Z
Learning: Mobile app (exactly/mobile) uses React Native, Expo, Tamagui (UI), Expo Router (navigation), and TanStack Query (state management)
Applied to files:
package.json
📚 Learning: 2026-01-05T21:07:40.716Z
Learnt from: franm91
Repo: exactly/exa PR: 614
File: package.json:94-94
Timestamp: 2026-01-05T21:07:40.716Z
Learning: For the exactly/exa mobile app, native module dependencies (like react-native-gesture-handler, react-native-reanimated, etc.) should use versions that match Expo SDK's bundledNativeModules.json to ensure compatibility and stability. Don't suggest upgrading these packages to latest npm versions if they're aligned with the Expo SDK version in use.
Applied to files:
package.json
📚 Learning: 2026-01-08T19:54:10.673Z
Learnt from: cruzdanilo
Repo: exactly/exa PR: 627
File: substreams/src/lib.rs:54-71
Timestamp: 2026-01-08T19:54:10.673Z
Learning: In substreams/src/lib.rs in the map_exa_plugins function, the deduplication logic using `!seen.insert(address.to_vec())` is intentional. The first plugin installed for a new account is an owner plugin (not an exa plugin), so it must be filtered out. The negation ensures the first plugin is skipped and subsequent plugins (the actual exa plugins) are kept.
Applied to files:
substreams/package.json
🪛 LanguageTool
substreams/CHANGELOG.md
[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa accounts - [#627](https://gi...
(DASH_RULE)
[typographical] ~9-~9: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ store exa accounts - [#627](https://...
(DASH_RULE)
[typographical] ~11-~11: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa plugins - [#627](https://git...
(DASH_RULE)
[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 917 characters long)
Context: ...uzdanilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(EN_EXCESSIVE_EXCLAMATION)
[typographical] ~13-~13: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(DASH_RULE)
🔇 Additional comments (3)
package.json (1)
3-3: LGTM!Version bump and dependency update are consistent with the changelog and coordinated with other package updates in the PR.
Also applies to: 41-41
substreams/package.json (1)
3-3: LGTM!Minor version bump is consistent with the changelog entries documenting new features for mapping and storing exa accounts and plugins.
server/package.json (1)
64-64: LGTM!DevDependency update correctly reflects the substreams package version bump from 0.0.1 to 0.1.0, maintaining monorepo consistency.
CHANGELOG.md
Outdated
| - [#629](https://github.com/exactly/exa/pull/629) [`3dfcac5`](https://github.com/exactly/exa/commit/3dfcac555a8b6981802c758da512e75bb5918372) Thanks [@cruzdanilo](https://github.com/cruzdanilo)! - ⚡️ implement asset logo caching | ||
|
|
||
| - Updated dependencies []: | ||
| - @exactly/server@0.2.48 |
There was a problem hiding this comment.
Line length violations exceed 120 character limit.
Lines 7, 9, and 10 exceed the 120-character limit specified in the markdown coding guidelines. This appears to be an inherent issue with the changeset format that includes PR links, commit links, and author credits in a single line.
As per coding guidelines: "All lines in markdown files must be no longer than 120 characters"
Consider whether the changeset tooling can be configured to wrap long lines, or if an exception to the line-length rule should be documented for auto-generated changelog entries.
🤖 Prompt for AI Agents
In @CHANGELOG.md around lines 7 - 10, CHANGELOG.md contains lines exceeding the
120-character limit (notably the combined PR/commit/author entry and the
dependency line on lines 7, 9 and 10); fix by wrapping those long changelog
entries so no single line exceeds 120 characters—e.g., split the
PR/commit/author entry into multiple lines (PR link and commit link on one line,
description/author on the next) and break the dependency list items across
lines, or alternatively update the changeset generation config to emit wrapped
entries or record an exception to the line-length rule for autogenerated
changelog lines.
| - [#627](https://github.com/exactly/exa/pull/627) [`8dd17fd`](https://github.com/exactly/exa/commit/8dd17fdd4141b9538ef7ab07695872c26d1b6ac7) Thanks [@cruzdanilo](https://github.com/cruzdanilo)! - ✨ map exa accounts | ||
|
|
||
| - [#627](https://github.com/exactly/exa/pull/627) [`3c75c10`](https://github.com/exactly/exa/commit/3c75c10afb9427ecd429e64f494aa402af3c8c2c) Thanks [@cruzdanilo](https://github.com/cruzdanilo)! - ✨ store exa accounts | ||
|
|
||
| - [#627](https://github.com/exactly/exa/pull/627) [`2d4e0e7`](https://github.com/exactly/exa/commit/2d4e0e72653e097ca0b3eadefb782940376a28a0) Thanks [@cruzdanilo](https://github.com/cruzdanilo)! - ✨ map exa plugins | ||
|
|
||
| - [#627](https://github.com/exactly/exa/pull/627) [`4720f68`](https://github.com/exactly/exa/commit/4720f68bc4f424ec302245962c76019aa44c40d7) Thanks [@cruzdanilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database |
There was a problem hiding this comment.
Line length violations exceed 120 character limit.
All four changeset entries (lines 7, 9, 11, 13) exceed the 120-character limit specified in the markdown coding guidelines. Similar to the root CHANGELOG.md, this is an inherent formatting issue with the changeset tooling that generates lines containing PR links, commit links, author credits, and change descriptions.
As per coding guidelines: "All lines in markdown files must be no longer than 120 characters"
Note: The static analysis hints about em dashes (DASH_RULE) and excessive exclamation marks are false positives related to the changeset format and gitmoji usage—these can be safely ignored.
🧰 Tools
🪛 LanguageTool
[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa accounts - [#627](https://gi...
(DASH_RULE)
[typographical] ~9-~9: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ store exa accounts - [#627](https://...
(DASH_RULE)
[typographical] ~11-~11: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa plugins - [#627](https://git...
(DASH_RULE)
[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 917 characters long)
Context: ...uzdanilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(EN_EXCESSIVE_EXCLAMATION)
[typographical] ~13-~13: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(DASH_RULE)
cruzdanilo
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
ed949fc to
6860c98
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@common/CHANGELOG.md`:
- Line 5: Change the markdown heading "### Patch Changes" to lowercase "###
patch changes" in common/CHANGELOG.md so all narrative prose follows the
internal lowercase guideline; locate the heading line and replace the text while
preserving heading level and surrounding content.
- Around line 7-11: The changelog has a single list line starting with "- [`#631`]
[`12563e6`] Thanks [`@cruzdanilo`]..." that exceeds 120 characters; fix by either
soft-wrapping that list item into multiple lines (split the PR/commit/author
portion onto its own indented line(s) while keeping the dash list marker) or add
a Markdown lint exception comment (e.g., disable MD013) immediately before the
item to allow the long line; update the "- [`#631`] ..." list item in CHANGELOG.md
accordingly.
♻️ Duplicate comments (3)
substreams/CHANGELOG.md (2)
5-5: Use lowercase for heading text per coding guidelines.The heading should be
### minor changesto comply with the guideline requiring all narrative text in internal documentation prose to be lowercase.Proposed fix
-### Minor Changes +### minor changesBased on learnings, all prose in internal markdown files must be lowercase.
7-13: Line length violations exceed 120 character limit.All four changeset entries exceed the 120-character limit specified in markdown coding guidelines. This is an inherent formatting limitation of the Changesets tooling.
Note: The static analysis hints about em dashes and excessive exclamation marks are false positives—these are standard Changesets format and gitmoji usage.
CHANGELOG.md (1)
3-49: Release changelog entries are complete and accurate.The 1.1.0 release documentation correctly captures:
- Minor changes: major dependency upgrades (Expo 52→54, React 18→19, wagmi 2→3, etc.)
- Patch changes: various fixes and improvements from PRs
#629,#633,#634- Updated dependencies:
@exactly/common@0.0.11,@exactly/server@0.2.49The long line lengths (exceeding 120 characters) are an inherent limitation of the Changesets auto-generated format, as previously noted.
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (28)
.changeset/breezy-planes-repeat.md.changeset/eleven-mangos-sing.md.changeset/flat-books-mix.md.changeset/forty-hornets-carry.md.changeset/lemon-baboons-agree.md.changeset/metal-states-divide.md.changeset/mighty-coins-fly.md.changeset/modern-pens-take.md.changeset/polite-turtles-glow.md.changeset/rare-readers-tell.md.changeset/red-toys-pump.md.changeset/shiny-cars-check.md.changeset/shiny-lies-beg.md.changeset/swift-waves-dance.md.changeset/true-items-juggle.md.changeset/violet-poems-heal.md.changeset/wacky-melons-decide.md.changeset/wild-carrots-fold.md.maestro/package.jsonCHANGELOG.mdcommon/CHANGELOG.mdcommon/package.jsondocs/package.jsonpackage.jsonserver/CHANGELOG.mdserver/package.jsonsubstreams/CHANGELOG.mdsubstreams/package.json
💤 Files with no reviewable changes (18)
- .changeset/eleven-mangos-sing.md
- .changeset/breezy-planes-repeat.md
- .changeset/violet-poems-heal.md
- .changeset/red-toys-pump.md
- .changeset/metal-states-divide.md
- .changeset/wacky-melons-decide.md
- .changeset/modern-pens-take.md
- .changeset/forty-hornets-carry.md
- .changeset/wild-carrots-fold.md
- .changeset/mighty-coins-fly.md
- .changeset/true-items-juggle.md
- .changeset/rare-readers-tell.md
- .changeset/lemon-baboons-agree.md
- .changeset/flat-books-mix.md
- .changeset/shiny-lies-beg.md
- .changeset/polite-turtles-glow.md
- .changeset/swift-waves-dance.md
- .changeset/shiny-cars-check.md
🧰 Additional context used
📓 Path-based instructions (2)
**/*.md
📄 CodeRabbit inference engine (.cursor/rules/markdown.mdc)
**/*.md: Each markdown file must start with a single top-level heading (# heading 1)
Headings must be sequential (e.g.,#->##->###), do not skip levels
Do not end headings with punctuation (.,:,!,?)
Use a hyphen (-) for unordered list items in markdown
Sub-lists in markdown must be indented with a two-space offset
Always use unordered lists (-) instead of numbered lists (1.) in markdown
All code blocks must be fenced with backticks (```) and specify a language identifier
Useshor `bash` as the language identifier for shell commands in markdown code blocks
All code identifiers inside backticks or code fences must strictly follow casing rules defined in `style.mdc` (`camelCase` for variables, `PascalCase` for types, etc.)
All code comments must be lowercase
All lines in markdown files must be no longer than 120 characters
Surround all block-level elements (headings, lists, code blocks) with a single blank line in markdown
Do not add multiple consecutive blank lines in markdown files
No lines should have trailing whitespace in markdown files
Use asterisks (`word`) for italics and double asterisks (`word`) for bold in markdown
Provide descriptive titles for links in markdown instead of generic phrases like 'click here'Use proper sentence case for user-facing documentation in the
docs/directory
Files:
substreams/CHANGELOG.mdserver/CHANGELOG.mdcommon/CHANGELOG.mdCHANGELOG.md
**/*.{mdc,md}
📄 CodeRabbit inference engine (.cursor/rules/style.mdc)
**/*.{mdc,md}: All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Any identifier inside backticks or code fences must strictly follow the casing rules defined in the style guide and be treated as code, not prose
Files:
substreams/CHANGELOG.mdserver/CHANGELOG.mdcommon/CHANGELOG.mdCHANGELOG.md
🧠 Learnings (18)
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/.changeset/*.md : Use a lowercase sentence in the imperative present tense for changeset summaries
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : All narrative text in internal documentation prose (headings, paragraphs, list items, proper nouns, brand names) must be lowercase with no exceptions
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: When implementing changes, follow all rules in `.mdc` files for any code, documentation, or rules you create, including meta-rules like the lowercase prose convention
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:58:16.574Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-23T19:58:16.574Z
Learning: All internal documentation and commit messages must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All code comments must be lowercase
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to docs/**/*.md : Use proper sentence case for all user-facing documentation in `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{ts,tsx,js,jsx} : All code comments must be lowercase; special tags (TODO, FIXME) are uppercase followed by a single space and lowercase comment, without colons or dashes, and should include a ticket/issue reference when available
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.{mdc,md} : When discussing code concepts in prose, use regular lowercase words and place correctly-cased identifiers inside backticks
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-30T15:03:28.449Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/style.mdc:0-0
Timestamp: 2025-12-30T15:03:28.449Z
Learning: Applies to **/*.md : Use proper sentence case for user-facing documentation in the `docs/` directory
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2025-12-23T19:57:22.339Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/markdown.mdc:0-0
Timestamp: 2025-12-23T19:57:22.339Z
Learning: Applies to **/*.md : All lines in markdown files must be no longer than 120 characters
Applied to files:
substreams/CHANGELOG.mdCHANGELOG.md
📚 Learning: 2026-01-09T16:24:21.227Z
Learnt from: cruzdanilo
Repo: exactly/exa PR: 627
File: .changeset/breezy-planes-repeat.md:5-5
Timestamp: 2026-01-09T16:24:21.227Z
Learning: In the exactly/exa repository, changeset summaries in .changeset/*.md files must include the gitmoji and follow the format `<emoji> <message>` (without the scope), matching the commit message format `<emoji> <scope>: <message>` but omitting the `<scope>:` portion.
Applied to files:
substreams/CHANGELOG.md
📚 Learning: 2026-01-08T19:54:15.788Z
Learnt from: cruzdanilo
Repo: exactly/exa PR: 627
File: substreams/src/lib.rs:54-71
Timestamp: 2026-01-08T19:54:15.788Z
Learning: In substreams/src/lib.rs in the map_exa_plugins function, the deduplication logic using `!seen.insert(address.to_vec())` is intentional. The first plugin installed for a new account is an owner plugin (not an exa plugin), so it must be filtered out. The negation ensures the first plugin is skipped and subsequent plugins (the actual exa plugins) are kept.
Applied to files:
substreams/package.json
📚 Learning: 2026-01-05T21:07:40.716Z
Learnt from: franm91
Repo: exactly/exa PR: 614
File: package.json:94-94
Timestamp: 2026-01-05T21:07:40.716Z
Learning: For the exactly/exa mobile app, native module dependencies (like react-native-gesture-handler, react-native-reanimated, etc.) should use versions that match Expo SDK's bundledNativeModules.json to ensure compatibility and stability. Don't suggest upgrading these packages to latest npm versions if they're aligned with the Expo SDK version in use.
Applied to files:
.maestro/package.jsonpackage.jsonCHANGELOG.md
📚 Learning: 2025-12-23T19:57:07.685Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/docs.mdc:0-0
Timestamp: 2025-12-23T19:57:07.685Z
Learning: Applies to docs/**/*.astro : Ensure best practices for writing .astro files and components using `plugin:astro/recommended` ESLint configuration
Applied to files:
docs/package.json
📚 Learning: 2025-12-23T19:57:07.685Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/docs.mdc:0-0
Timestamp: 2025-12-23T19:57:07.685Z
Learning: Applies to docs/**/*.astro : All documentation must be built with Astro and the Starlight theme
Applied to files:
docs/package.json
📚 Learning: 2025-12-23T19:56:56.405Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/dev.mdc:0-0
Timestamp: 2025-12-23T19:56:56.405Z
Learning: Mobile app (exactly/mobile) uses React Native, Expo, Tamagui (UI), Expo Router (navigation), and TanStack Query (state management)
Applied to files:
package.jsonCHANGELOG.md
📚 Learning: 2025-12-23T19:58:16.574Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-23T19:58:16.574Z
Learning: React Native mobile app (`app`) stack: use react native, expo, tamagui, and tanstack query
Applied to files:
CHANGELOG.md
📚 Learning: 2025-12-23T19:56:56.405Z
Learnt from: CR
Repo: exactly/exa PR: 0
File: .cursor/rules/dev.mdc:0-0
Timestamp: 2025-12-23T19:56:56.405Z
Learning: Server (exactly/server) uses Hono (framework), Node.js, Drizzle ORM (database), and PostgreSQL
Applied to files:
server/package.json
🪛 LanguageTool
substreams/CHANGELOG.md
[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa accounts - [#627](https://gi...
(DASH_RULE)
[typographical] ~9-~9: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ store exa accounts - [#627](https://...
(DASH_RULE)
[typographical] ~11-~11: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ map exa plugins - [#627](https://git...
(DASH_RULE)
[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 917 characters long)
Context: ...uzdanilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(EN_EXCESSIVE_EXCLAMATION)
[typographical] ~13-~13: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ✨ insert exa plugins into database
(DASH_RULE)
common/CHANGELOG.md
[typographical] ~7-~7: Consider using an em dash in dialogues and enumerations.
Context: ...danilo](https://github.com/cruzdanilo)! - ⬆️ centralize eslint flat config, upgra...
(DASH_RULE)
🔇 Additional comments (9)
substreams/package.json (1)
3-3: LGTM!The version bump from
0.0.1to0.1.0correctly reflects the minor release for the new exa accounts and plugins features documented in the changelog.common/package.json (1)
3-3: LGTM!The version bump to
0.0.11correctly reflects the patch release for the ESLint flat config centralization..maestro/package.json (1)
15-15: LGTM!The
@exactly/commondependency update toworkspace:^0.0.11correctly aligns with the common package version bump in this PR.server/CHANGELOG.md (1)
3-8: LGTM!The new 0.2.49 patch entry is properly formatted and consistent with the existing changelog structure. The version bump aligns with the server/package.json update.
docs/package.json (1)
19-20: LGTM!Workspace dependency versions correctly updated to align with the new releases:
@exactly/[email protected]and@exactly/[email protected].package.json (2)
3-3: LGTM!Version bump from 1.0.45 to 1.1.0 correctly reflects the minor release scope described in the PR objectives.
37-39: Workspace dependencies updated correctly.The
@exactly/commonand@exactly/serverworkspace references are consistent with the released versions across the monorepo.server/package.json (2)
3-3: LGTM!Server version correctly bumped to 0.2.49, matching the changelog entry.
63-65: DevDependencies updated correctly.Workspace references for
@exactly/common(0.0.11) and@exactly/substreams(0.1.0) are consistent with the release versions.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
|
|
||
| ## 0.0.11 | ||
|
|
||
| ### Patch Changes |
There was a problem hiding this comment.
Use lowercase for heading text per coding guidelines.
The heading should be ### patch changes to comply with the guideline requiring all narrative text in internal documentation prose to be lowercase.
Proposed fix
-### Patch Changes
+### patch changesBased on learnings, all prose in internal markdown files must be lowercase.
📝 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.
| ### Patch Changes | |
| ### patch changes |
🤖 Prompt for AI Agents
In `@common/CHANGELOG.md` at line 5, Change the markdown heading "### Patch
Changes" to lowercase "### patch changes" in common/CHANGELOG.md so all
narrative prose follows the internal lowercase guideline; locate the heading
line and replace the text while preserving heading level and surrounding
content.
cruzdanilo
force-pushed
the
changeset-release/main
branch
from
6860c98 to
ce12331
Compare
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
@exactly/[email protected]
Minor Changes
#627
8dd17fdThanks @cruzdanilo! - ✨ map exa accounts#627
3c75c10Thanks @cruzdanilo! - ✨ store exa accounts#627
2d4e0e7Thanks @cruzdanilo! - ✨ map exa plugins#627
4720f68Thanks @cruzdanilo! - ✨ insert exa plugins into database@exactly/[email protected]
Minor Changes
12563e6Thanks @cruzdanilo! - ⬆️ major upgrades:@account-kit/*replacing@alchemy/aa-*eslint.config.mjsPatch Changes
#634
4269f4fThanks @franm91! - ✨ add benefits section#633
b43570bThanks @cruzdanilo! - ♻️ replace user operations with eip-5792 calls#634
0ddaccdThanks @franm91! - ➕ install carousel and gesture handler#629
3dfcac5Thanks @cruzdanilo! - ⚡️ implement asset logo caching#633
52b1872Thanks @cruzdanilo! - 💄 fix scroll view styling#633
721996bThanks @cruzdanilo! - 🐛 fix parse units scientific notation crash#633
6d50a19Thanks @cruzdanilo! - 🚸 improve browser opening across platforms#633
cb8fbdaThanks @cruzdanilo! - ♿️ improve asset selector accessibility#633
49d0378Thanks @cruzdanilo! - ⚡️ prefer expo image#633
f324725Thanks @cruzdanilo! - ✨ support eip-5792 in account client#633
8a67e30Thanks @cruzdanilo! - 🐛 switch chain on transfer#633
d390381Thanks @cruzdanilo! - 💄 fix card switch height#633
1bf1360Thanks @cruzdanilo! - 🔥 remove connection indicatorUpdated dependencies [
12563e6,12563e6]:@exactly/[email protected]
Patch Changes
12563e6Thanks @cruzdanilo! - ⬆️ centralize eslint flat config, upgrade account-kiteslint/:base.mjs: core config with typescript-eslint strict-type-checked, unicorn, regexp, import, nx, prettier, jsdoc/tsdocnode.mjs: node.js config with eslint-plugin-n, security, vitestreact.mjs: react config with @eslint-react strict-type-checked, tanstack-query, jsx-a11y@exactly/[email protected]
Patch Changes
12563e6Thanks @cruzdanilo! - ⬆️ new eslint config, upgrade vitest, account-kit, and other dependenciesSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.