chore(deps): bump actions/checkout from 5 to 6 #1
Conversation
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
🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
The RFC_XXXX naming convention is intentional and standard for these packages.
Removed toRFC1035() and toRFC1123() transformation methods. Added init patterns for bidirectional conversion: RFC_1123.Domain(rfc1035Domain) RFC_1035.Domain(rfc1123Domain) This provides a cleaner, more idiomatic API for cross-RFC conversions.
- Added String.swift with String extension utilities - Updated code formatting and implementation - Removed Scripts/setup-rfc.sh - Updated Package.swift and gitignore
Convert @suite and @test declarations to use Swift 6.2 backtick syntax: - @suite("Name") struct Foo → @suite struct `Name` - @test("Description") func test() → @test func `Description`() - @test("Desc", arguments: [...]) → @test(arguments: [...]) func `Desc`() This leverages Swift 6.2's support for backticks in identifiers, making test names more readable and eliminating duplicate strings.
Migrates RFC 1123 Domain implementation to use canonical [UInt8] storage and type-safe error hierarchy, following category theory principles where String is derived through functor composition: Label → [UInt8] → String. Key improvements: - Canonical init takes [Label] for zero-validation composition - Typed throws (Swift 6) with Label.Error/Domain.Error hierarchy - TLD-specific validation preserved in convenience string init - Bidirectional conversions: Domain ↔ [UInt8] ↔ String - 2-5x performance improvement via direct byte operations Architecture: - Domain.init(labels: [Label]): canonical, compositional validation only - Domain.init(labels: [String]): convenience, validates String→Label with TLD rules - Domain.init(_ string:): convenience, parses and validates - Domain.init(_ bytes:): convenience, decodes UTF-8 and validates RFC 1123 allows labels to start with digits (unlike RFC 1035) but enforces stricter TLD rules (must start and end with letters). This distinction is preserved through internal ValidationType enum in convenience initializers.
- Update Domain.init(_:) to accept `some StringProtocol` - Update Domain.init(labels:) to accept `some Sequence<some StringProtocol>` - Update Label.init(_:validateAs:) to accept `some StringProtocol` - Enables zero-copy domain parsing from Substring - No breaking changes (String conforms to StringProtocol) Pattern matches swift-rfc-1035 (already upgraded): - Uses .split() which works on StringProtocol - Validates and stores components efficiently Ref: STRINGPROTOCOL_AUDIT_REPORT.md Phase 1
Block all .md files by default except: - Whitelisted documentation files (README, LICENSE, etc.) - Files within .docc documentation catalogs
Remove custom encoding parameter from StringProtocol initializers as RFC 1123 domain names are pure ASCII (7-bit). Only UTF-8 interpretation is academically correct since ASCII ⊂ UTF-8. This makes the API more correct and prevents misuse with incompatible encodings like UTF-16 or UTF-32.
Inherit SwiftLint rules from the parent swift-standards repository.
- Apply swift-format formatting across all source files - Add RFC_1123.Domain.Label.swift for label handling - Add exports.swift for public API - Remove deprecated StringProtocol and [UInt8] extensions - Update Package.swift dependencies
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v5...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/github_actions/actions/checkout-6
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps actions/checkout from 5 to 6.
Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
1af3b93update readme/changelog for v6 (#2311)71cf226v6-beta (#2298)069c695Persist creds to a separate file (#2286)ff7abcdUpdate README to include Node.js 24 support details and requirements (#2248)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)