1
0
mirror of synced 2025-12-30 12:02:01 -05:00

Remove deprecated GHES versions from content and data (#15830)

* ran script/remove-unused-assets.js (manually removed unused variables printed by the script)

* package-lock

* turn elsif into two ifs to prepare for running Liquid deprecation script

* ran script/remove-deprecated-enterprise-version-markup.js --release 2.14 (ONLY UPDATES LINE BREAKS ETC.)

* ran script/remove-deprecated-enterprise-version-markup.js --release 2.15

* ran script/remove-deprecated-enterprise-version-markup.js --release 2.17

* ran script/remove-deprecated-enterprise-version-markup.js --release 2.18

* update hardcoded test

* Update content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>

* add currentVersion is NOT free-pro-team to conditional, to make sure the deprecation script does the right thing when it is time to deprecate 2.21

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
This commit is contained in:
Sarah Schneider
2020-10-01 10:55:34 -04:00
committed by GitHub
parent dc5b6f2670
commit f272eec944
355 changed files with 346 additions and 566 deletions

View File

@@ -1 +1 @@
This guide shows you how to create a workflow that publishes Java packages to {% data variables.product.prodname_registry %} and the Maven Central Repository. With a single workflow, you can publish packages to a single repository or to multiple repositories.
This guide shows you how to create a workflow that publishes Java packages to {% data variables.product.prodname_registry %} and the Maven Central Repository. With a single workflow, you can publish packages to a single repository or to multiple repositories.