$ cd konveyor-core
[jmatthews@mbp2024] in ~/synced/konveyor-core (main) $ git log | head
commit 63de6d11968bb05987a2197102bf6083c1e234ab
Author: Shawn Hurley <shawn@hurley.page>
Date: Mon Apr 20 16:14:58 2026 -0400
feat: add prop_type_changes field to FixStrategyEntry
Add a new BTreeMap<String, Vec<MappingEntry>> field to capture per-prop
Testing PR konveyor-ecosystem/semver-analyzer#21
$ time ./run.sh --migrate ./quipucords-ui --base-branch original_2.1.0 --non-interactive
[ERROR] Required command not found: unbuffer
[ERROR] Script failed with exit code 1 (0s)
[ERROR] Check logs in /Users/jmatthews/synced/hack_semver/example_runs/2026_05_18/patternfly-tools/logs/20260518T210546/ for details
| $ time ./build.sh | |
| PatternFly Tools Builder | |
| ======================== | |
| [INFO] Checking build prerequisites... | |
| [INFO] All build prerequisites satisfied | |
| [INFO] Host platform: Mac_arm64 | |
| Select target platform: |
git remote add pranavgaikwad https://github.com/pranavgaikwad/semver-analyzer.git
git fetch pranavgaikwad
git checkout -b pranav/addBuildScripts pranavgaikwad/feat/addBuildScripts
export SEMVER_REPO_BRANCH=feat/addBuildScripts
export SEMVER_REPO_URL=https://github.com/pranavgaikwad/semver-analyzer.git
./build.sh
Welcome to the PatternFly MCP Server codebase. This guide will help you understand what this project does, how it's organized, and how to navigate it confidently.
This is a Model Context Protocol (MCP) server that gives AI assistants (like Claude, Copilot, etc.) structured access to PatternFly design system documentation, component schemas, and guidelines. Think of it as a smart, searchable library that an LLM can query to get accurate PatternFly information while helping developers write code.
In practical terms: when a developer using an AI assistant asks "how do I use the PatternFly Button component?", this server provides the AI with the actual PatternFly docs and JSON schemas rather than relying on potentially outdated training data.
This MCP server provides 22 tools across 7 classes that help AI agents build Quarkus applications. The Quarkus-specific information it delivers comes from 6 distinct sources, each gathered differently.
LLMs are stateless and non-deterministic. Every decision an agent makes is determined entirely by the tokens currently in its context window. The implication is stark: better tokens in, better tokens out. And critically, more tokens does not mean better outcomes. DEV Community
Performance degrades beyond roughly 40% context utilization. As context usage grows, model quality degrades, often beginning around 40% of the window depending on task complexity. Common culprits: large tool outputs (JSON blobs, UUIDs, logs), unfiltered file dumps, long correction-loop histories, and MCPs dumping irrelevant data. Once you're in the dumb zone, model quality doesn't matter. Alexlavaee | [DEV Community](https://dev.to/
| <!DOCTYPE html><html lang="en-US"><head><title>semver-analyzer & fix-engine</title><meta property="og:title" content="semver-analyzer & fix-engine"><meta charset="UTF-8"><meta name="viewport" content="width=device-width,height=device-height,initial-scale=1.0"><meta name="apple-mobile-web-app-capable" content="yes"><meta http-equiv="X-UA-Compatible" content="ie=edge"><meta property="og:type" content="website"><meta name="twitter:card" content="summary"><style>@media screen{body[data-bespoke-view=""] .bespoke-marp-parent>.bespoke-marp-osc>button,body[data-bespoke-view=next] .bespoke-marp-parent>.bespoke-marp-osc>button,body[data-bespoke-view=overview] button.bespoke-marp-overview-close,body[data-bespoke-view=presenter] .bespoke-marp-presenter-container .bespoke-marp-presenter-info-container .bespoke-marp-presenter-info-page-area .bespoke-marp-presenter-info-page,body[data-bespoke-view=presenter] .bespoke-marp-presenter-container .bespoke-marp-presenter-info-container button,body[data-bespoke-view=presen |
PR: konveyor-ecosystem/semver-analyzer#17
Title: fix: co-generate fix guidance entries with rules to fix alignment bug
Branch: fix/fix-guidance-alignment-bug
Files changed: 3 (crates/ts/src/konveyor.rs, crates/ts/src/konveyor_v2.rs, src/main.rs)
Review date: 2026-05-07
This file is the TypeScript-specific Konveyor rule generator for the semver-analyzer project. It transforms a structured analysis report (AnalysisReport<TypeScript>) — which describes breaking API changes, behavioral changes, and manifest changes between two versions of a TypeScript/React component library — into machine-readable Konveyor rules and fix guidance that downstream tooling (Kantra) uses to detect and auto-fix migration issues in consumer codebases.
In concrete terms: given a diff between, say, PatternFly v5 and v6, this module produces YAML rule files that tell a static analysis engine "if a consumer imports <Modal> from @patternfly/react-core, flag it and provide this migration message."