Skip to content

chore(deps): february updates #746

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
basmasking wants to merge 2 commits into from
Closed

chore(deps): february updates #746

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f6d3bf6
#745: updated deps
basmasking Feb 1, 2026
179b9bc
#745: updated root version to match published one
basmasking Feb 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1,089 changes: 291 additions & 798 deletions documentation/package-lock.json
View file
Open in desktop

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion documentation/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@
"docs:preview": "vitepress preview docs"
},
"devDependencies": {
"vitepress": "2.0.0-alpha.15"
"vitepress": "2.0.0-alpha.16"
}
}
2 changes: 1 addition & 1 deletion examples/access-protection/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
Copy link

@coderabbitai coderabbitai bot Feb 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

jitar 0.10.5 release notes breaking changes

💡 Result:

I couldn’t find any Jitar (MaskingTechnology/jitar) release/tag v0.10.5—the repo’s tags jump from v0.10.0 / v0.10.1 / v0.10.2 (latest shown) and there’s no v0.10.5 to pull release notes from. [1]

If you actually meant Digdag 0.10.5 (often the top hit for this query), its 0.10.5 notes list “General Changes / Fixed Issues / UI Changes” and do not call out any breaking changes. [2]

Which “jitar” do you mean (GitHub repo / npm package link)? If you share the URL, I can extract the exact 0.10.5 breaking changes (if that version exists for it).

Sources: [1] [2]

🏁 Script executed:

# Examine the examples/access-protection structure
find examples/access-protection -type f -name "*.json" -o -name "*.js" -o -name "*.ts" | head -20

Repository: MaskingTechnology/jitar

Length of output: 679

🏁 Script executed:

# Check how jitar is used in the example
rg "jitar\|gateway\|worker" examples/access-protection/ -A 2 -B 2

Repository: MaskingTechnology/jitar

Length of output: 49

🏁 Script executed:

# Read the package.json to confirm the version
cat examples/access-protection/package.json

Repository: MaskingTechnology/jitar

Length of output: 719

🌐 Web query:

jitar npm package versions registry

💡 Result:

  • Package: jitar (npm)
  • Latest version (per Libraries.io): 0.9.3 (install: npm i jitar@0.9.3) [1]

List versions from the npm registry

The default npm registry is https://registry.npmjs.org [2]. To list all published versions:

npm view jitar versions --json

(npm view <pkg> versions returns the available versions) [3]

See dist-tags (e.g., latest)

npm dist-tag ls jitar

(latest is the default tag installed by npm install jitar) [4]

Sources: [1] https://libraries.io/npm/jitar [2] https://docs.npmjs.com/cli/v11/using-npm/registry [3] https://blog.packagecloud.io/how-to-inspect-download-and-extract-npm-packages/ [4] https://docs.npmjs.com/cli/v7/commands/npm-dist-tag

🏁 Script executed:

# Query npm registry directly to list all jitar versions
npm view jitar versions --json 2>/dev/null | python3 << 'EOF'
import json
import sys
data = json.load(sys.stdin)
print("All available jitar versions:")
for v in sorted(data):
    print(f"  {v}")
print(f"\nTotal versions: {len(data)}")
print(f"Latest: {data[-1]}")
print(f"\n0.10.5 exists: {'0.10.5' in data}")
EOF

Repository: MaskingTechnology/jitar

Length of output: 787

Fix jitar version: 0.10.5 does not exist.

jitar 0.10.5 is not available in the npm registry (latest: 0.9.3) or GitHub repository (latest tag: v0.10.2). Update to a valid version or the example services (gateway/worker) will fail to install and start.

🤖 Prompt for AI Agents 
In `@examples/access-protection/package.json` at line 19, The package.json
dependency "jitar": "0.10.5" is invalid; update the jitar version to a valid
published tag (e.g., "0.10.2" or the npm latest "0.9.3") so the example services
(gateway/worker) can install and start; modify the "jitar" entry in
examples/access-protection/package.json to one of these valid versions.

}
}
2 changes: 1 addition & 1 deletion examples/data-transportation/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
}
}
2 changes: 1 addition & 1 deletion examples/error-handling/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
Copy link

@coderabbitai coderabbitai bot Feb 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

jitar 0.10.5 npm release notes changelog breaking changes

💡 Result:

There is no jitar@0.10.5 release on npm, and there is no v0.10.5 tag/release in the upstream GitHub repo.

  • npm: the latest published version is 0.9.3 (and the npm version history shown there does not include any 0.10.x versions). [1]
  • GitHub: the repo has tags up to v0.10.2 (no v0.10.5). [2]
  • GitHub Releases: the project does not use GitHub “Releases” (so there are no release-note pages there). [3]

If you meant another package, or you meant jitar@0.10.2 (Git tag) or jitar@0.9.3 (npm), tell me which one and I’ll pull the relevant changelog/breaking-change notes for that version.

Sources: [1] (npmjs.com) [2] (github.com) [3] (github.com)

Citations:

Update jitar dependency to an existing version.

The version 0.10.5 does not exist. Latest npm version is 0.9.3 and latest Git tag is v0.10.2. Update the dependency to one of these available versions.

🤖 Prompt for AI Agents 
In `@examples/error-handling/package.json` at line 19, The package.json entry for
the "jitar" dependency references a non-existent version "0.10.5"; update the
version string in package.json (the "jitar" dependency line) to a valid release
such as the published npm version "0.9.3" or to the existing git-tagged release
"v0.10.2" (choose the one appropriate for your registry and install method).

}
}
2 changes: 1 addition & 1 deletion examples/health-checks/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
}
}
2 changes: 1 addition & 1 deletion examples/hello-world/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
}
}
2 changes: 1 addition & 1 deletion examples/load-balancing/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
}
}
2 changes: 1 addition & 1 deletion examples/middleware/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
}
}
2 changes: 1 addition & 1 deletion examples/multi-version/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
}
}
2 changes: 1 addition & 1 deletion examples/resources/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
Copy link

@coderabbitai coderabbitai bot Feb 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

jitar 0.10.5 release notes breaking changes

💡 Result:

I couldn’t find any project/package named “jitar” with a 0.10.5 release (or release notes) via web search.

The closest unambiguous match is Digdag 0.10.5. Its 0.10.5 release notes list general/API/UI improvements and fixes, but do not call out any breaking changes. [1]

If you’re upgrading and specifically worried about breakage in the 0.10.x line, the major breaking changes are documented in Digdag 0.10.0, including authentication configuration changes, removal of JWT authentication, and “some API have been abolished and changed.” [2]

Sources: [1] [2]

🏁 Script executed:

cat examples/resources/package.json

Repository: MaskingTechnology/jitar

Length of output: 497

🏁 Script executed:

find . -iname "*changelog*" -o -iname "*releases*" -o -iname "*release-notes*" | head -20

Repository: MaskingTechnology/jitar

Length of output: 688

🏁 Script executed:

rg -i "0\.10\.5|breaking\s+change|migration" --type md --type txt | head -40

Repository: MaskingTechnology/jitar

Length of output: 2489

🏁 Script executed:

git log --oneline --all --grep="jitar\|0\.10" | head -20

Repository: MaskingTechnology/jitar

Length of output: 1390

🏁 Script executed:

cat CHANGELOG.md | head -100

Repository: MaskingTechnology/jitar

Length of output: 4986

🏁 Script executed:

grep -A 20 "## \[0\.10" CHANGELOG.md | head -80

Repository: MaskingTechnology/jitar

Length of output: 49

🏁 Script executed:

find examples/resources -type f -name "*.json" -o -name "*.ts" -o -name "*.js" | xargs rg "monitor" -i

Repository: MaskingTechnology/jitar

Length of output: 51

🏁 Script executed:

git tag | grep "0\.10"

Repository: MaskingTechnology/jitar

Length of output: 49

🏁 Script executed:

git branch -a | grep "0\.10"

Repository: MaskingTechnology/jitar

Length of output: 49

Update jitar to 0.10.3 (the latest released version in the 0.10.x series).

The specified version 0.10.5 does not exist. The CHANGELOG and git history show the latest 0.10.x release is 0.10.3 (2025-11-20). Using a non-existent version will cause the build to fail during npm install.

🤖 Prompt for AI Agents 
In `@examples/resources/package.json` at line 16, The package.json currently pins
the dependency "jitar" to a non-existent version "0.10.5"; update the dependency
value for the "jitar" entry to the latest available 0.10.x release "0.10.3" so
npm install resolves correctly and the build won't fail.

}
}
2 changes: 1 addition & 1 deletion examples/segmentation/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@
"typescript": "5.9.3"
},
"dependencies": {
"jitar": "0.10.4"
"jitar": "0.10.5"
}
}
Loading