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

Release Tracking #1839

Merged
merged 1 commit into from
Feb 28, 2023
Merged

Release Tracking #1839

merged 1 commit into from
Feb 28, 2023

Conversation

primer-css
Copy link
Collaborator

@primer-css primer-css commented Feb 22, 2023

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@primer/[email protected]

Minor Changes

Patch Changes

@github-actions
Copy link
Contributor

github-actions bot commented Feb 22, 2023

❗ Pre-merge checklist

Please ensure these items are checked before merging.

🔎 Smoke test

  • All CI checks pass
  • Docs and Lookbook open in a browser
  • Successful integration test with GitHub.com as a primary consumer of Primer View Components
    • Install the npm release candidate in npm-workspaces/primer/
    • Use bin/vendor-gem to update primer_view_components gem
    • Verify no new build errors appear
    • Verify no new linting errors appear
    • Manually test critical paths
    • Manually test release-specific bugfixes and/or features work as described

🤔 Sanity test

  • All bugfixes in this release have resolved their corresponding issues
  • All new features in this release have been tested and verified as compatible with GitHub.com
  • No noticeable regressions have been introduced as a result of changes in this release
  • Release notes accurately describe the changes made

Please also leave any testing notes as a comment on this pull request. In particular, describing any issues encountered during your testing. This is helpful in providing historical context to maintainers.

@primer-css primer-css force-pushed the changeset-release/main branch from 551d046 to 687e04c Compare February 22, 2023 20:13
@primer-css primer-css temporarily deployed to preview February 22, 2023 20:13 — with GitHub Actions Inactive
@primer-css primer-css temporarily deployed to github-pages February 22, 2023 20:18 — with GitHub Actions Inactive
@primer-css primer-css force-pushed the changeset-release/main branch from 687e04c to 3a735b1 Compare February 23, 2023 18:05
@primer-css primer-css temporarily deployed to github-pages February 23, 2023 18:09 — with GitHub Actions Inactive
@primer-css primer-css force-pushed the changeset-release/main branch from 3a735b1 to 63897fd Compare February 23, 2023 18:13
@primer-css primer-css temporarily deployed to github-pages February 23, 2023 18:17 — with GitHub Actions Inactive
@primer-css primer-css temporarily deployed to preview February 24, 2023 19:35 — with GitHub Actions Inactive
@primer-css primer-css temporarily deployed to github-pages February 24, 2023 19:35 — with GitHub Actions Inactive
@camertron
Copy link
Contributor

Dotcom PR (internal only): https://github.com/github/github/pull/261707

@camertron camertron merged commit bd6aa6f into main Feb 28, 2023
@camertron camertron deleted the changeset-release/main branch February 28, 2023 19:00
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.

2 participants