chore: bump version references to v1.1.0 - #6
Merged
Conversation
Signed-off-by: Krishan Kant Sharma <krishansharma0327@gmail.com>
- Homepage terminal animation: flaglint v1.0.0 → v1.1.0 - json-output.md baseline example: flaglintVersion 1.0.0 → 1.1.0 Signed-off-by: Krishan Kant Sharma <krishansharma0327@gmail.com>
Deploying flaglint with
|
| Latest commit: |
ab29241
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a8ae618f.flaglint.pages.dev |
| Branch Preview URL: | https://chore-bump-version-1-1-0.flaglint.pages.dev |
📝 WalkthroughWalkthroughUpdates the displayed FlagLint version from 1.0.0 to 1.1.0 in three locations: a guide's verification badge, a JSON baseline example in reference documentation, and the homepage hero terminal demo. ChangesVersion String Update
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/pages/index.astro`:
- Line 909: The hero terminal label is still hardcoded with a fixed version
string instead of using the shared package-derived value. Update the
`index.astro` template where the `term-version` span is rendered to use the
existing `version` variable so the displayed app version stays in sync with
`package.json` and the rest of the page.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 25f195d5-9a9a-41f2-ae43-ea47261b1104
📒 Files selected for processing (3)
src/content/docs/docs/guides/launchdarkly-to-openfeature-nodejs.mdsrc/content/docs/docs/reference/json-output.mdsrc/pages/index.astro
| <span class="dot green"></span> | ||
| </div> | ||
| <span class="term-version">flaglint v1.0.0</span> | ||
| <span class="term-version">flaglint v1.1.0</span> |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use the shared version value here.
This header still hardcodes v1.1.0 even though the file already derives version from package.json. Wiring the terminal label to version keeps the hero demo in sync and avoids the next drift.
♻️ Proposed fix
- <span class="term-version">flaglint v1.1.0</span>
+ <span class="term-version">flaglint v{version}</span>📝 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.
Suggested change
| <span class="term-version">flaglint v1.1.0</span> | |
| <span class="term-version">flaglint v{version}</span> |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/pages/index.astro` at line 909, The hero terminal label is still
hardcoded with a fixed version string instead of using the shared
package-derived value. Update the `index.astro` template where the
`term-version` span is rendered to use the existing `version` variable so the
displayed app version stays in sync with `package.json` and the rest of the
page.
This was referenced Jul 6, 2026
flaglint
pushed a commit
that referenced
this pull request
Jul 8, 2026
…trict-types and baseline counts Every identity-resolution gap listed as "not resolved yet" on the flaglint-go Limitations and Supported Scope pages has actually been closed (verified directly against the flaglint-go issue tracker): chained factory-call-then-method (#20), method values (#6), interface satisfaction (#15), block-scoped shadowing (#5), factory returning a wrapper type (#16), and nested go.mod files (#17). These pages were last updated right before that work landed. - limitations.md / supported-scope.md: mark all six as resolved (noting which layer resolves each — Phase 1 default vs. opt-in --strict-types), add two newer Phase-1 mechanisms these pages never mentioned at all (a struct field declared *ld.LDClient with no observed construction, and a composite literal directly initializing a package-level var), and state plainly that zero identity-resolution gaps are currently tracked. - identity-model.md: add worked examples for both newer Phase-1 mechanisms above, plus a new "Phase 2 — --strict-types" section (interface satisfaction, transitive factory wrapping, cross-function method-value forwarding) that didn't exist on this page at all before. - index.md: same corrections to the "what flaglint-go does/doesn't do" summary — it previously named method values and interface satisfaction as open gaps. - cli/{scan,audit,validate}.md: --strict-types wasn't documented as a flag anywhere on the site despite being available on all three commands since it shipped; added to each page's options table. audit.md's baseline JSON example was also missing the "schemaVersion" and "counts" fields flaglint-go now emits; validate.md's Baseline Mode section gains a note on what "counts" actually catches (a brand-new duplicate of an already-baselined call, not just a brand-new fingerprint). Verified: `npm run build` completes cleanly (90 pages), spot-checked the rendered Limitations page's output directly. Signed-off-by: Krishan Kant Sharma <krishansharma0327@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
flaglint v1.0.0→flaglint v1.1.0flaglintVersion: "1.0.0"→"1.1.0"Test plan
flaglint v1.1.0Summary by CodeRabbit