Skip to content
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.

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

Update .spi.yml #2679

Merged
merged 1 commit into from
Dec 22, 2023
Merged

Update .spi.yml #2679

merged 1 commit into from
Dec 22, 2023

Conversation

finestructure
Copy link
Contributor

Not sure what the intent was for these changes but I believe they're what made the 5.7...5.8 builds being flagged as incompatible on SPI.

SwiftPackageIndex/SwiftPackageIndex-Server#2798 (comment)

- documentation_targets: [ComposableArchitecture]
swift_version: 5.9
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This instance of swift_version was only necessary to make docs being built with 5.9 when 5.8 was the default. By removing it, docs will still be built with 5.9 and will automatically move to use 5.10 etc once those become available.

@@ -3,15 +3,10 @@ builder:
configs:
- platform: ios
scheme: ComposableArchitecture
swift_version: 5.9
Copy link
Contributor Author

Choose a reason for hiding this comment

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

What swift_version does here is it constrains the scheme config to ios and 5.9 where previously it applied to all iOS builds. You almost certainly don't want this here or in the other configs below.

@finestructure finestructure marked this pull request as draft December 22, 2023 12:41
@finestructure
Copy link
Contributor Author

Ok, this isn't the whole story. xcrun xcodebuild -resolvePackageDependencies also fails when running it with 5.8 against 1.5.6 and I need to investigate why.

@stephencelis
Copy link
Member

@finestructure This good to go now?

@finestructure
Copy link
Contributor Author

Yes! I won't fix things by itself but is required to make the other fix work.

@stephencelis stephencelis merged commit 718f1d8 into pointfreeco:main Dec 22, 2023
cgrindel-self-hosted-renovate bot added a commit to cgrindel/rules_swift_package_manager that referenced this pull request Jan 9, 2024
…ure to from: "1.6.0" (#842)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
|
[pointfreeco/swift-composable-architecture](https://togithub.com/pointfreeco/swift-composable-architecture)
| minor | `from: "1.5.6"` -> `from: "1.6.0"` |

---

### Release Notes

<details>
<summary>pointfreeco/swift-composable-architecture
(pointfreeco/swift-composable-architecture)</summary>

###
[`v1.6.0`](https://togithub.com/pointfreeco/swift-composable-architecture/releases/tag/1.6.0)

[Compare
Source](https://togithub.com/pointfreeco/swift-composable-architecture/compare/1.5.6...1.6.0)

#### What's Changed

- Added: `TestStore.receive(\.action, payload)` for asserting against
the payload of an action without requiring the action itself be
`Equatable`
([pointfreeco/swift-composable-architecture#2669;
[pointfreeco/swift-composable-architecture#2691)
- Fixed: It was possible for `ViewStore`s to ping their
`objectWillChange` publisher during a body computation, triggering a
SwiftUI warning. This has been fixed
([pointfreeco/swift-composable-architecture#2688).
- Fixed: `@Reducer` macro no longer automatically applies
`@CasePathable` macro to enums with explicit conformance (thanks
[@&#8203;scogeo](https://togithub.com/scogeo),
[pointfreeco/swift-composable-architecture#2685).
- Fixed: The `prepareDependencies` closure is now only performed a
single time when creating a store, not every single time an action is
received
([pointfreeco/swift-composable-architecture#2695).
- Fixed: A retain cycle in `PresentationModifier` has been fixed
([pointfreeco/swift-composable-architecture#2697).
- Performance: Clean up parent/child store invalidation checks
([pointfreeco/swift-composable-architecture#2674).
- Infrastructure: Fix package build in 5.7 for SPI
([pointfreeco/swift-composable-architecture#2675;
thanks [@&#8203;finestructure](https://togithub.com/finestructure),
[pointfreeco/swift-composable-architecture#2679).
- Infrastructure: Typo fix (thanks
[@&#8203;tomokisun](https://togithub.com/tomokisun),
[pointfreeco/swift-composable-architecture#2678).
- Infrastructure: Add documentation around new store scoping
characteristics
([pointfreeco/swift-composable-architecture#2676).
- Infrastructure: Prevent unnecessary tutorial diffs (thanks
[@&#8203;bricklife](https://togithub.com/bricklife),
[pointfreeco/swift-composable-architecture#2692).
- Infrastructure: Tutorial fixes
([pointfreeco/swift-composable-architecture#2693).
- Infrastructure : Clean up shared state case study
([pointfreeco/swift-composable-architecture#2696).

#### New Contributors

- [@&#8203;bricklife](https://togithub.com/bricklife) made their first
contribution in
[pointfreeco/swift-composable-architecture#2692

**Full Changelog**:
pointfreeco/swift-composable-architecture@1.5.6...1.6.0

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config help](https://togithub.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://togithub.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi4xMDAuMCIsInVwZGF0ZWRJblZlciI6IjM2LjEwMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->

Co-authored-by: Self-hosted Renovate Bot <361546+cgrindel-self-hosted-renovate[bot]@users.noreply.github.enterprise.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants