Bump @ttsc/lint from 0.21.0 to 0.23.0 in the typescript group

[dependabot]

Bumps the typescript group with 1 update: @ttsc/lint.

Updates @ttsc/lint from 0.21.0 to 0.23.0

Release notes

Sourced from @​ttsc/lint's releases.

v0.23.0

   🐞 Bug Fixes

• Close residual project-input, CI, graph, and runtime liveness gaps  -  by @​samchon in samchon/ttsc#1017 (10693)
• Close factory, config, and playground liveness gaps  -  by @​samchon in samchon/ttsc#1024 (bc3e2)
• Close final watch, documentation, and CI runtime gaps  -  by @​samchon in samchon/ttsc#1030 (b5000)
• Close final Windows watch and maintenance gaps  -  by @​samchon in samchon/ttsc#1034 (f3b59)
• release: Make Go SDK extraction portable on Windows  -  by @​samchon in samchon/ttsc#1026 (79c76)
• unplugin: Derive watch inputs once per envelope generation  -  by @​samchon (1dab1)

    View changes on GitHub

v0.22.0

   🚀 Features

• lint:
  • Declare project-rule external inputs  -  by @​samchon (23beb)
  • Make project-rule inputs live across watch sessions  -  by @​samchon and Claude Opus 4.8 (1M context) in samchon/ttsc#1001 (be564)

   🐞 Bug Fixes

• lint:
  • Harden project input snapshots  -  by @​samchon (986d0)
  • Anchor project input snapshots  -  by @​samchon (4906e)
  • Validate Windows project input namespaces  -  by @​samchon (c1540)
• ttsc:
  • Watch declared project-rule inputs  -  by @​samchon (74d15)
  • Harden external input watch lifecycle  -  by @​samchon (0eed7)
  • Rebind replaced project input watchers  -  by @​samchon (9c3de)
  • Preserve queued project input events  -  by @​samchon (52d11)
  • Make project input watches event-complete  -  by @​samchon (fffcd)
  • Refresh project diagnostics for external inputs  -  by @​samchon (a73b4)
  • Reuse resident programs in check watch  -  by @​samchon (d45ba)
  • Make external input watches replacement-safe  -  by @​samchon (39428)
  • Ignore empty project input watch baselines  -  by @​samchon (84489)
  • Keep project input watches event-driven  -  by @​samchon (f6d5b)
  • Preserve resident check generations  -  by @​samchon (5ce39)
  • Validate project input filesystem roots  -  by @​samchon (5243b)
  • Reconcile rejected project input watches  -  by @​samchon (20f19)
  • Retain deltas for duplicate resident entries  -  by @​samchon (8b8bc)
  • Model effective compiler output options  -  by @​samchon (53599)
  • Deduplicate nested project input watches  -  by @​samchon (4d415)
  • Preserve project input filesystem identities  -  by @​samchon (00554)
  • Preserve watch correctness across topology changes  -  by @​samchon (ba663)
  • Separate data changes from execution reloads  -  by @​samchon (1ec5d)
  • Honor compiler configuration semantics  -  by @​samchon (edc4b)
  • Align watch topology with compiler outputs  -  by @​samchon (f3fbe)
  • Unify project input filesystem identities  -  by @​samchon (c95b0)
  • Close project input identity boundaries  -  by @​samchon (21a35)
  • Bind watch events to reflected generations  -  by @​samchon (a9aba)

... (truncated)

Commits

• 2684908 chore: release v0.23.0
• f3b5998 fix: close final Windows watch and maintenance gaps (#1034)
• b50009b fix: close final watch, documentation, and CI runtime gaps (#1030)
• 79c7611 fix(release): make Go SDK extraction portable on Windows (#1026)
• bc3e2e9 fix: close factory, config, and playground liveness gaps (#1024)
• 1069333 fix: close residual project-input, CI, graph, and runtime liveness gaps (#1017)
• 05b7e25 Merge pull request #1009 from samchon/fix/watch-derivation-scaling
• 976d6c3 test(nestia): assert checkout structure without shell parsing
• c693234 test(nestia): preserve shell token semantics
• 15f728b test(nestia): cover workflow-wide and shell ownership
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	webpack@​5.109.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: packages/backend/package.json → npm/webpack@5.109.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.109.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report