Port Documentation/PackageRegistry directory contents into DocC
#8745
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
- Added more descriptions to the subcommands for registry - Refactored links that were navigating to the proposal for registry and instead link them to the subcommands in our DocC catalog
|
@swift-ci please test |
bripeticca
requested review from
jakepetroules,
dschaefer2,
shawnhyam,
plemarquand,
owenv,
bkhouri,
cmcgee1024 and
daveyc123
as code owners
heckj
reviewed
Jun 10, 2025
There was a problem hiding this comment.
Lots of wording changes - the vast majority of which are:
- reframing from passive voice to active voice
- replacing latin abbreviations
- changing the capitalization of "Package manager" to "package manger" and sometimes adding "the" in front to make it read smoothly.
Sources/PackageManagerDocs/Documentation.docc/PackageCollections.md
Outdated
Show resolved
Hide resolved
Sources/PackageManagerDocs/Documentation.docc/PackageCollections.md
Outdated
Show resolved
Hide resolved
Sources/PackageManagerDocs/Documentation.docc/PackageCollections.md
Outdated
Show resolved
Hide resolved
Sources/PackageManagerDocs/Documentation.docc/PackageCollections.md
Outdated
Show resolved
Hide resolved
Sources/PackageManagerDocs/Documentation.docc/PackageSecurity.md
Outdated
Show resolved
Hide resolved
Sources/PackageManagerDocs/Documentation.docc/PackageSecurity.md
Outdated
Show resolved
Hide resolved
Sources/PackageManagerDocs/Documentation.docc/PackageSecurity.md
Outdated
Show resolved
Hide resolved
Sources/PackageManagerDocs/Documentation.docc/PackageSecurity.md
Outdated
Show resolved
Hide resolved
Sources/PackageManagerDocs/Documentation.docc/PackageSecurity.md
Outdated
Show resolved
Hide resolved
|
@swift-ci please test |
|
@swift-ci please test |
|
@swift-ci please test windows |
heckj
approved these changes
Jun 16, 2025
Comment on lines
8
to
11
| Author a package collection as a static JSON document and publish it to the web or distribute it on a local file system. | ||
|
|
||
| Educators and community influencers can publish package collections to go along with course materials or blog posts, making it easier for their readers to use packages for the first time, or choosing which packages to use for a particular task. | ||
| Enterprises may use collections to provide a trusted set of packages, or a collection of packages consistently used by a team. |
There was a problem hiding this comment.
Suggested change
| Author a package collection as a static JSON document and publish it to the web or distribute it on a local file system. | |
| Educators and community influencers can publish package collections to go along with course materials or blog posts, making it easier for their readers to use packages for the first time, or choosing which packages to use for a particular task. | |
| Enterprises may use collections to provide a trusted set of packages, or a collection of packages consistently used by a team. | |
| Educators and community influencers can publish package collections to go along with course materials or blog posts, making it easier for their readers to use packages for the first time, or choosing which packages to use for a particular task. | |
| Enterprises may use collections to provide a trusted set of packages, or a collection of packages consistently used by a team. | |
| Author a package collection as a static JSON document and publish it to the web or distribute it on a local file system. |
What do you think of this as one paragraph? I think the "author this by..." stuff may read a little better after we've described the two use cases.
There was a problem hiding this comment.
I think it reads a lot better this way! I'll upload a change for this :)
Migrate, and break up, content from `documentation/plugins.md` into DocC articles. resolves swiftlang#8592 With the branch checked out, you can use the command: ```bash swift package --disable-sandbox preview-documentation --target PackageManagerDocs ``` To build and display the collected documentation for easier reviewing. --------- Co-authored-by: Bri Peticca <[email protected]>
Command plugins should use the user specified build system when building any dependencies, and if the command plugin requests a build of its own. Supporting the full range of command plugin functionality with the Swift Build backend will take a little more work, but this patch gets the fundamentals wired up
We should avoid adding a dependency on Swift Tools Support Core in SwiftPM. If we need to, we ought to use the `swiftTSCBasicsDeps` and `swiftToolsCoreSupportAutoDeps` variables.
### Motivation: I hope that this should fix swiftlang#8731, and make it easier to build with libFuzzer. ### Modifications: Add support for a `-sanitize=fuzzer` option in `swift-build`, that sets the correct flags (including `-parse-as-library`) to build a binary for fuzzing. Add an additional test to make sure that these flags get set.
…ature flags The build system requested by the `swift package migrate` command is transitory and shouldn't be persisted. This would also make sure that the build plan is always available regardless of what builds happened before `swift package migrate` invocation. Resolves: rdar://152687084
It's currently impossible to distringuish between modules that are created from the declarations in a manifest and the ones synthesized as part of module graph building and/or build plan creation. This was only a problem for `SystemLibraryModule` before, but with the introduction of `swift package migrate` command the situation changed because the command can only operate on modules that appear in the manifest file because it won't be possible to update code or settings of the synthesized modules.
Fixes and setting updates to such modules cannot be applied. Resolves: rdar://152689053
|
@swift-ci please test |
|
@swift-ci please test windows |
|
@swift-ci please test macOS |
|
@swift-ci please test |
|
@swift-ci please test windows |
1 similar comment
|
@swift-ci please test windows |
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.
Fixes #8596 and fixes #8597.