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

Security advisory documentation #5458

Closed
1 task done
szakarias opened this issue Jan 12, 2024 · 0 comments · Fixed by #5485
Closed
1 task done

Security advisory documentation #5458

szakarias opened this issue Jan 12, 2024 · 0 comments · Fixed by #5485
Assignees
Labels
co.request Community ask for documentation dev.packages Relates to package publishing e2-days Can complete in < 5 days of normal, not dedicated, work p2-medium Necessary but not urgent concern. Resolve when possible.

Comments

@szakarias
Copy link
Contributor

szakarias commented Jan 12, 2024

What information needs to be added?

Add documentation about security advisories in pub

Where should this new content appear?

No response

I would like to fix this problem.

  • I will try and fix this problem on dart.dev.
@szakarias szakarias added from.user Issue raised by user co.request Community ask for documentation labels Jan 12, 2024
@szakarias szakarias self-assigned this Jan 12, 2024
@parlough parlough added p2-medium Necessary but not urgent concern. Resolve when possible. e2-days Can complete in < 5 days of normal, not dedicated, work dev.packages Relates to package publishing and removed from.user Issue raised by user labels Jan 12, 2024
parlough added a commit that referenced this issue Jan 24, 2024
Follow-up to #5480

Fixes #5458

A few things:

- Adjusts the placeholder redirect to point to the new page
- Add a cross-link from the pubspec reference page
- Fixes a few typos
- Use descriptive link text instead of "Here"
- Remove `/en` from the GitHub link, so it's more likely redirect to the
desired language of the user
- In the "Ignoring security advisories" section, if putting the pubspec
field `ignored_advisories` in code font, it's not really "a list of
`ignored_advisories`, but rather a list itself.
- Uses proper capitalization for "GitHub"
- Use "the Dart team" instead of "we" for the recommendation
- Some other minor wording adjustments _(please take a look :])_
atsansone pushed a commit to atsansone/site-www that referenced this issue Jan 26, 2024
Follow-up to dart-lang#5480

Fixes dart-lang#5458

A few things:

- Adjusts the placeholder redirect to point to the new page
- Add a cross-link from the pubspec reference page
- Fixes a few typos
- Use descriptive link text instead of "Here"
- Remove `/en` from the GitHub link, so it's more likely redirect to the
desired language of the user
- In the "Ignoring security advisories" section, if putting the pubspec
field `ignored_advisories` in code font, it's not really "a list of
`ignored_advisories`, but rather a list itself.
- Uses proper capitalization for "GitHub"
- Use "the Dart team" instead of "we" for the recommendation
- Some other minor wording adjustments _(please take a look :])_
atsansone pushed a commit to atsansone/site-www that referenced this issue Feb 20, 2024
Follow-up to dart-lang#5480

Fixes dart-lang#5458

A few things:

- Adjusts the placeholder redirect to point to the new page
- Add a cross-link from the pubspec reference page
- Fixes a few typos
- Use descriptive link text instead of "Here"
- Remove `/en` from the GitHub link, so it's more likely redirect to the
desired language of the user
- In the "Ignoring security advisories" section, if putting the pubspec
field `ignored_advisories` in code font, it's not really "a list of
`ignored_advisories`, but rather a list itself.
- Uses proper capitalization for "GitHub"
- Use "the Dart team" instead of "we" for the recommendation
- Some other minor wording adjustments _(please take a look :])_
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co.request Community ask for documentation dev.packages Relates to package publishing e2-days Can complete in < 5 days of normal, not dedicated, work p2-medium Necessary but not urgent concern. Resolve when possible.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants