Change:
<del> { "registrations": [ { "component": { "type": "other", "other": { "name": "octicons-code", "version": "3.1.0", "downloadUrl": "https://registry.npmjs.org/octicons/-/octicons-3.1.0.tgz" } }, "licenseDetail": [ "The MIT License (MIT)", "", "(c) 2012-2015 GitHub", "", "Permission is hereby granted, free of charge, to any person obtaining a copy", "of this software and associated documentation files (the "Software"), to deal", "in the Software without restriction, including without limitation the rights", "to use, copy, modify, merge, publish, distribute, sublicense, and/or sell", "copies of the Software, and to permit persons to whom the Software is", "furnished to do so, subject to the following conditions:", "", "The above copyright notice and this permission notice shall be included in", "all copies or substantial portions of the Software.", "", "THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR", "IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,", "FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE", "AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER", "LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,", "OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN", "THE SOFTWARE." ], "license": "MIT", "version": "3.1.0" }, { "component": { "type": "other", "other": { "name": "octicons-font", "version": "3.1.0", "downloadUrl": "https://registry.npmjs.org/octicons/-/octicons-3.1.0.tgz" } }, "licenseDetail": [ "(c) 2012-2015 GitHub", "", "SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007", "", "PREAMBLE", "The goals of the Open Font License (OFL) are to stimulate worldwide", "development of collaborative font projects, to support the font creation", "efforts of academic and linguistic communities, and to provide a free and", "open framework in which fonts may be shared and improved in partnership", "with others.", "", "The OFL allows the licensed fonts to be used, studied, modified and", "redistributed freely as long as they are not sold by themselves. The", "fonts, including any derivative works, can be bundled, embedded,", "redistributed and/or sold with any software provided that any reserved", "names are not used by derivative works. The fonts and derivatives,", "however, cannot be released under any other type of license. The", "requirement for fonts to remain under this license does not apply", "to any document created using the fonts or their derivatives.", "", "DEFINITIONS", ""Font Software" refers to the set of files released by the Copyright", "Holder(s) under this license and clearly marked as such. This may", "include source files, build scripts and documentation.", "", ""Reserved Font Name" refers to any names specified as such after the", "copyright statement(s).", "", ""Original Version" refers to the collection of Font Software components as", "distributed by the Copyright Holder(s).", "", ""Modified Version" refers to any derivative made by adding to, deleting,", "or substituting -- in part or in whole -- any of the components of the", "Original Version, by changing formats or by porting the Font Software to a", "new environment.", "", ""Author" refers to any designer, engineer, programmer, technical", "writer or other person who contributed to the Font Software.", "", "PERMISSION & CONDITIONS", "Permission is hereby granted, free of charge, to any person obtaining", "a copy of the Font Software, to use, study, copy, merge, embed, modify,", "redistribute, and sell modified and unmodified copies of the Font", "Software, subject to the following conditions:", "", "1) Neither the Font Software nor any of its individual components,", "in Original or Modified Versions, may be sold by itself.", "", "2) Original or Modified Versions of the Font Software may be bundled,", "redistributed and/or sold with any software, provided that each copy", "contains the above copyright notice and this license. These can be", "included either as stand-alone text files, human-readable headers or", "in the appropriate machine-readable metadata fields within text or", "binary files as long as those fields can be easily viewed by the user.", "", "3) No Modified Version of the Font Software may use the Reserved Font", "Name(s) unless explicit written permission is granted by the corresponding", "Copyright Holder. This restriction only applies to the primary font name as", "presented to the users.", "", "4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font", "Software shall not be used to promote, endorse or advertise any", "Modified Version, except to acknowledge the contribution(s) of the", "Copyright Holder(s) and the Author(s) or with their explicit written", "permission.", "", "5) The Font Software, modified or unmodified, in part or in whole,", "must be distributed entirely under this license, and must not be", "distributed under any other license. The requirement for fonts to", "remain under this license does not apply to any document created", "using the Font Software.", "", "TERMINATION", "This license becomes null and void if any of the above conditions are", "not met.", "", "DISCLAIMER", "THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,", "EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF", "MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT", "OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE", "COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,", "INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL", "DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING", "FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM", "OTHER DEALINGS IN THE FONT SOFTWARE." ], "license": "SIL OFL 1.1", "version": "3.1.0" } ], "version": 1 } </del>

Discussion:
Related to This issue is to track the progress of updating our version of (3.1.0) to the latest version (8.2.0). We'll need to create the work to convert the latest versions (svg) back into an icon font. Below are the requirements for this work: [x] Convert svgs into icon font [x] Include backward compatibility [x] Map old unicodes to new icons [x] Remove unnecessary font files [x] Add/update proper licenses [x] Test new icon font Working branch can be found under . Below is a list of the new additions: - - - - - - - - - - Please refer to for a full list of updates. :octocat: :heart:
Is this also going to address ?
this is only for addressing Octicons, which are only used in the status bar. will be likely be address when we get to , which I'm hoping to start on this iteration.

Unfortunately not so easy because some octicons have been removed and hence updating might likely break some extensions that rely on them
Is there a plan going forwards with this? I just tried to use an octicon and it came up blank. I couldn't work out why until I checked the versions being used, which led me here. From the change log, it looks like some of the removed icons are just renamed. Would it be possible to add a simple 'redirect' to return the new icon if the old name is used? Similarly, if an icon has genuinely been removed, could a placeholder be returned? In fact, it would probably be nicer to return something if a bad icon is named, rather than leaving a blank space.
Hm... Do you have a pointer/release notes that describe these changes?
I was just looking through here:
Yeah, so I believe we would miss two icons and we might wanna risk that... For the other we have alternatives in place... No promises, stretch for June (also accepting PRs)
Great - thanks!
So, this would be the compat table and the good news is that no extension seems to use those three removed icons. The bad news is that octicons are now shipped as npm module which we cannot consume at the level at which we define the
we already have all the octicon resources checked in to our sources, so why is the fact that Octicons now ship as an NPM module an issue for us moving forward? Can we not just do the same? !
Yeah, copying the node-module isn't the blocker, tho weird, the issue is more that it's not a font anymore but 150+ svg-files which we need to bundle in a clever way.
Maybe has an idea on how to do that. I wonder if we can convert the set back to a font so that it is easy for us to consume it as we did before.
and I talked about how to convert the new svgs back into an icon font. We'd need to setup a project (probably in node) that would have the right modules to convert svgs into icons.

but we'd need to: Format the octicons file names to include their unicode Format the less/sass templates to match the old styles format Audit the changes from the old version of Octicons (renames/deletions/additions) Map all of the changes Also create local ttf file for users to install This would take some time to setup, but nonetheless it is very hacky. Github has already so this would be a patch that we'd need to maintain. One last thing to consider is if in the future we decide to create our own icon set (related to ) then this would be deprecated. I'd be in favor of putting our efforts into creating our own icon set that can be consumed by everyone.