PostgreSQL 歷史版本列表 Page10

更新時間：2021-02-16
更新細節：

What's new in this version:

New:
- Export downloads to text or CSV file
- Add custom metadata to video and audio downloads
- Change the filename for single video downloads
- Added a new setting to remove downloads from the list once they are complete

Improvements:
- Improved playlist/channel extraction for YouTube, Vimeo, and Dailymotion
- The name of the video quality will no longer be appended to filenames. However, you can enable it manually from the Downloads tab in Settings.

Fixed
- Fixed downloads from CNN
- Other minor bug fixes

更新時間：2021-02-16
更新細節：

What's new in this version:

- Improved performance on macOS Big Sur

Updated:
- Babel, Babel plugins and presets to 7.12.16
- Less to 4.1.1
- PostCSS to 8.2.6
- Autoprefixer to 10.2.4
- Dart Sass to 1.32.7
- Terser to 5.6.0
- TypeScript to 4.1.5

更新時間：2021-02-12
更新細節：

What's new in this version:

- Fix failure to check per-column SELECT privileges in some join queries
- In some cases involving joins, the parser failed to record all the columns read by a query in the column-usage bitmaps that are used for permissions checking. Although the executor would still insist on some sort of SELECT privilege to run the query, this meant that a user having SELECT privilege on only one column of a table could nonetheless read all its columns through a suitably crafted query.
- A stored view that is subject to this problem will have incomplete column-usage bitmaps, and thus permissions will still not be enforced properly on the view after updating. In installations that depend on column-level permissions for security, it is recommended to CREATE OR REPLACE all user-defined views to cause them to be re-parsed.
- The PostgreSQL Project thanks Sven Klemm for reporting this problem. (CVE-2021-20229)
- Fix information leakage in constraint-violation error messages
- If an UPDATE command attempts to move a row to a different partition but finds that it violates some constraint on the new partition, and the columns in that partition are in different physical positions than in the parent table, the error message could reveal the contents of columns that the user does not have SELECT privilege on. (CVE-2021-3393)
- Fix incorrect detection of concurrent page splits while inserting into a GiST index
- Concurrent insertions could lead to a corrupt index with entries placed in the wrong pages. It's recommended to reindex any GiST index that's been subject to concurrent insertions.
- Fix CREATE INDEX CONCURRENTLY to wait for concurrent prepared transactions
- At the point where CREATE INDEX CONCURRENTLY waits for all concurrent transactions to complete so that it can see rows they inserted, it must also wait for all prepared transactions to complete, for the same reason. Its failure to do so meant that rows inserted by prepared transactions might be omitted from the new index, causing queries relying on the index to miss such rows. In installations that have enabled prepared transactions (max_prepared_transactions > 0), it's recommended to reindex any concurrently-built indexes in case this problem occurred when they were built.
- Avoid crash when trying to rescan an aggregation plan node that has both hashed and sorted grouping sets
- Fix possible incorrect query results when a hash aggregation node spills some tuples to disk
- It was possible for aggregation grouping values to be replaced by nulls when the tuples are read back in, leading to wrong answers.
- Fix edge case in incremental sort
- If the last tuple of a sort batch chanced to be the first tuple of the next group of already-sorted tuples, the code did the wrong thing. This could lead to “retrieved too many tuples in a bounded sort” error messages, or to silently-wrong sorting results.
- Avoid crash when a CALL or DO statement that performs a transaction rollback is executed via extended query protocol
- In PostgreSQL 13, this case reliably caused a null-pointer dereference. In earlier versions the bug seems to have no visible symptoms, but it's not quite clear that it could never cause a problem.
- Avoid unnecessary errors with BEFORE UPDATE triggers on partitioned tables
- A BEFORE UPDATE FOR EACH ROW trigger that modified the row in any way prevented UPDATE from moving the row to another partition when needed; but there is no longer any reason for this restriction.
- Fix partition pruning logic to handle asymmetric hash partition sets
- If a hash-partitioned table has unequally-sized partitions (that is, varying modulus values), or it lacks partitions for some remainder values, then the planner's pruning logic could mistakenly conclude that some partitions don't need to be scanned, leading to failure to find rows that the query should find.
- Avoid incorrect results when WHERE CURRENT OF is applied to a cursor whose plan contains a MergeAppend node
- This case is unsupported (in general, a cursor using ORDER BY is not guaranteed to be simply updatable); but the code previously did not reject it, and could silently give false matches.
- Fix crash when WHERE CURRENT OF is applied to a cursor whose plan contains a custom scan node
- Fix planner's mishandling of placeholders whose evaluation should be delayed by an outer join
- This occurs in particular with trivial subqueries containing lateral references to outer-join outputs. The mistake could result in a malformed plan. The known cases trigger a “failed to assign all NestLoopParams to plan nodes” error, but other symptoms may be possible.
- Fix planner's handling of placeholders during removal of useless RESULT RTEs
- This oversight could lead to “no relation entry for relid N” planner errors.
- Fix planner's handling of a placeholder that is computed at some join level and used only at that same level
- This oversight could lead to “failed to build any N-way joins” planner errors.
- Consider unsorted subpaths when planning a Gather Merge operation
- It's possible to use such a path by adding an explicit Sort node, and in some cases that gives rise to a superior plan.
- Do not consider ORDER BY expressions involving parallel-restricted functions or set-returning functions when trying to parallelize sorts
- Such cases cannot safely be pushed into worker processes, but the incremental sort feature accidentally made us consider them.
- Be more careful about whether index AMs support mark/restore
- This prevents errors about missing support functions in rare edge cases.
- Fix overestimate of the amount of shared memory needed for parallel queries
- Fix ALTER DEFAULT PRIVILEGES to handle duplicated arguments safely
- Duplicate role or schema names within the same command could lead to “tuple already updated by self” errors or unique-constraint violations.
- Flush ACL-related caches when pg_authid changes
- This change ensures that permissions-related decisions will promptly reflect the results of ALTER ROLE ... [NO] INHERIT.
- Fix failure to detect “snapshot too old” conditions in tables rewritten in the current transaction
- This is only a hazard when wal_level is set to minimal and the rewrite is performed by ALTER TABLE SET TABLESPACE.
- Fix spurious failure of CREATE PUBLICATION when applied to a table created or rewritten in the current transaction
- This is only a hazard when wal_level is set to minimal.
- Prevent misprocessing of ambiguous CREATE TABLE LIKE clauses
- A LIKE clause is re-examined after initial creation of the new table, to handle importation of indexes and such. It was possible for this re-examination to find a different table of the same name, causing unexpected behavior; one example is where the new table is a temporary table of the same name as the LIKE target.
- Rearrange order of operations in CREATE TABLE LIKE so that indexes are cloned before building foreign key constraints
- This fixes the case where a self-referential foreign key constraint declared in the outer CREATE TABLE depends on an index that's coming from the LIKE clause.
- Disallow CREATE STATISTICS on system catalogs
- Disallow converting an inheritance child table to a view
- Ensure that disk space allocated for a dropped relation is released promptly at commit
- Previously, if the dropped relation spanned multiple 1GB segments, only the first segment was truncated immediately. Other segments were simply unlinked, which doesn't authorize the kernel to release the storage so long as any other backends still have the files open.
- Prevent dropping a tablespace that is referenced by a partitioned relation, but is not used for any actual storage
- Previously this was allowed, but subsequent operations on the partitioned relation would fail.
- Fix progress reporting for CLUSTER
- Fix handling of backslash-escaped multibyte characters in COPY FROM
- A backslash followed by a multibyte character was not handled correctly. In some client character encodings, this could lead to misinterpreting part of a multibyte character as a field separator or end-of-copy-data marker.
- Avoid preallocating executor hash tables in EXPLAIN without ANALYZE
- Fix recently-introduced race condition in LISTEN/NOTIFY queue handling
- A newly-listening backend could attempt to read SLRU pages that were in process of being truncated, possibly causing an error.
- Allow the jsonb concatenation operator to handle all combinations of JSON data types
- We can concatenate two JSON objects or two JSON arrays. Handle other cases by wrapping non-array inputs in one-element arrays, then performing an array concatenation. Previously, some combinations of inputs followed this rule but others arbitrarily threw an error.
- Fix use of uninitialized value while parsing a * quantifier in a BRE-mode regular expression
- This error could cause the quantifier to act non-greedy, that is behave like a *? quantifier would do in full regular expressions.
- Fix numeric power() for the case where the exponent is exactly INT_MIN (-2147483648)
- Previously, a result with no significant digits was produced.
- Fix integer-overflow cases in substring() functions
- If the specified starting index and length overflow an integer when added together, substring() misbehaved, either throwing a bogus “negative substring length” error for a case that should succeed, or failing to complain that a negative length is negative (and instead returning the whole string, in most cases).
- Prevent possible data loss from incorrect detection of the wraparound point of an SLRU log
- The wraparound point typically falls in the middle of a page, which must be rounded off to a page boundary, and that was not done correctly. No issue could arise unless an installation had gotten to within one page of SLRU overflow, which is unlikely in a properly-functioning system. If this did happen, it would manifest in later “apparent wraparound” or “could not access status of transaction” errors.
- Fix WAL-reading logic to handle timeline switches correctly
- Previously, if WAL archiving is enabled, a standby could fail to follow a primary running on a newer timeline, with errors like “requested WAL segment has already been removed”.
- Fix memory leak in walsender processes while sending new snapshots for logical decoding
- Fix relation cache leak in walsender processes while sending row changes via the root of a partitioned relation during logical replication (Amit Langote, Mark Zhao)
- Fix walsender to accept additional commands after terminating replication
- Ensure detection of deadlocks between hot standby backends and the startup (WAL-application) process
- The startup process did not run the deadlock detection code, so that in situations where the startup process is last to join a circular wait situation, the deadlock might never be recognized.
- Fix possible failure to detect recovery conflicts while deleting an index entry that references a HOT chain
- The code failed to traverse the HOT chain and might thus compute a too-old XID horizon, which could lead to incorrect conflict processing in hot standby. The practical impact of this bug is limited; in most cases the correct XID horizon would be found anyway from nearby operations.
- Ensure that a nonempty value of krb_server_keyfile always overrides any setting of KRB5_KTNAME in the server's environment
- Previously, which setting took precedence depended on whether the client requests GSS encryption.
- In server log messages about failing to match connections to pg_hba.conf entries, include details about whether GSS encryption has been activated
- This is relevant data if hostgssenc or hostnogssenc entries exist.
- Fix assorted issues in server's support for GSS encryption
- Remove pointless restriction that only GSS authentication can be used on a GSS-encrypted connection. Add GSS encryption information to connection-authorized log messages. Include GSS-related space when computing the required size of shared memory (this omission could have caused problems with very high max_connections settings). Avoid possible infinite recursion when reporting an unrecoverable GSS encryption error.
- Ensure that unserviced requests for background workers are cleaned up when the postmaster begins a “smart” or “fast” shutdown sequence
- Previously, there was a race condition whereby a child process that had requested a background worker just before shutdown could wait indefinitely, preventing shutdown from completing.
- Fix portability problem in parsing of recovery_target_xid values
- The target XID is potentially 64 bits wide, but it was parsed with strtoul(), causing misbehavior on platforms where long is 32 bits (such as Windows).
- Avoid trying to use parallel index build in a standalone backend
- Allow index AMs to support included columns without necessarily supporting multiple key columns
- While taking a base backup, avoid executing any SHA256 code if a backup manifest is not needed
- When using OpenSSL operating in FIPS mode, SHA256 hashing is rejected, leading to an error. This change makes it possible to take a base backup on such a platform, so long as --no-manifest is specified.
- Avoid assertion failure during parallel aggregation of an aggregate with a non-strict deserialization function
- No such aggregate functions exist in core PostgreSQL, but some extensions such as PostGIS provide some. The mistake is harmless anyway in a non-assert build.
- Avoid assertion failure in pg_get_functiondef() when examining a function with a TRANSFORM option
- Fix data structure misallocation in PL/pgSQL's CALL statement
- A CALL in a PL/pgSQL procedure, to another procedure that has OUT parameters, would fail if the called procedure did a COMMIT or ROLLBACK.
- In libpq, do not skip trying SSL after GSS encryption
- If we successfully made a GSS-encrypted connection, but then failed during authentication, we would fall back to an unencrypted connection rather than next trying an SSL-encrypted connection. This could lead to unexpected connection failure, or to silently getting an unencrypted connection where an encrypted one is expected. Fortunately, GSS encryption could only succeed if both client and server hold valid tickets in the same Kerberos infrastructure. It seems unlikely for that to be true in an environment that requires SSL encryption instead.
- Make libpq's PQconndefaults() function report the correct default value for channel_binding
- In psql, re-allow including a password in a connection_string argument of a connect command
- This used to work, but a recent bug fix caused the password to be ignored (resulting in prompting for a password).
- In psql's d commands, don't truncate the display of column default values
- Formerly, they were arbitrarily truncated at 128 characters.
- Fix assorted bugs in psql's help command
- help with two argument words failed to find a command description using only the first word, for example help reset all should show the help for RESET but did not. Also, help often failed to invoke the pager when it should. It also leaked memory.
- Fix pg_dump's dumping of inherited generated columns
- The previous behavior resulted in (harmless) errors during restore.
- In pg_dump, ensure that the restore script runs ALTER PUBLICATION ADD TABLE commands as the owner of the publication, and similarly runs ALTER INDEX ATTACH PARTITION commands as the owner of the partitioned index
- Previously, these commands would be run by the role that started the restore script; which will usually work, but in corner cases that role might not have adequate permissions.
- Fix pg_dump to handle WITH GRANT OPTION in an extension's initial privileges
- If an extension's script creates an object and grants privileges on it with grant option, then later the user revokes such privileges, pg_dump would generate incorrect SQL for reproducing the situation. (Few if any extensions do this today.)
- In pg_rewind, ensure that all WAL is accounted for when rewinding a standby server
- In pgbench, disallow a digit as the first character of a variable name
- This prevents trying to substitute variables into timestamp literal values, which may contain strings like 12:34.
- Report the correct database name in connection failure error messages from some client programs
- If the database name was defaulted rather than given on the command line, pg_dumpall, pgbench, oid2name, and vacuumlo would produce misleading error messages after a connection failure.
- Fix memory leak in contrib/auto_explain
- Memory consumed while producing the EXPLAIN output was not freed until the end of the current transaction (for a top-level statement) or the end of the surrounding statement (for a nested statement). This was particularly a problem with log_nested_statements enabled.
- In contrib/postgres_fdw, avoid leaking open connections to remote servers when a user mapping or foreign server object is dropped
- Open connections that depend on a dropped user mapping or foreign server can no longer be referenced, but formerly they were kept around anyway for the duration of the local session.
- Fix faulty assertion in contrib/postgres_fdw
- In contrib/pgcrypto, check for error returns from OpenSSL's EVP functions
- We do not really expect errors here, but this change silences warnings from static analysis tools.
- Make contrib/pg_prewarm more robust when the cluster is shut down before prewarming is complete
- Previously, autoprewarm would rewrite its status file with only the block numbers that it had managed to load so far, thus perhaps largely disabling the prewarm functionality in the next startup. Instead, suppress status file updates until the initial loading pass is complete.
- In contrib/pg_trgm's GiST index support, avoid crash in the rare case that picksplit is called on exactly two index items
- Fix miscalculation of timeouts in contrib/pg_prewarm and contrib/postgres_fdw
- The main loop in contrib/pg_prewarm's autoprewarm parent process underestimated its desired sleep time by a factor of 1000, causing it to consume much more CPU than intended. When waiting for a result from a remote server, contrib/postgres_fdw overestimated the desired timeout by a factor of 1000 (though this error had been mitigated by imposing a clamp to 60 seconds).
- Both of these errors stemmed from incorrectly converting seconds-and-microseconds to milliseconds. Introduce a new API TimestampDifferenceMilliseconds() to make it easier to get this right in the future.
- Improve configure's heuristics for selecting PG_SYSROOT on macOS
- The new method is more likely to produce desirable results when Xcode is newer than the underlying operating system. Choosing a sysroot that does not match the OS version may result in nonfunctional executables.
- While building on macOS, specify -isysroot in link steps as well as compile steps
- This likewise improves the results when Xcode is out of sync with the operating system.
- Fix JIT compilation to be compatible with LLVM 11 and LLVM 12
- Fix potential mishandling of references to boolean variables in JIT expression compilation
- No field reports attributable to this have been seen, but it seems likely that it could cause problems on some architectures.
- Fix compile failure with ICU 68 and later
- Avoid memcpy() with a NULL source pointer and zero count during partitioned index creation
- While such a call is not known to cause problems in itself, some compilers assume that the arguments of memcpy() are never NULL, which could result in incorrect optimization of nearby code.
- Update time zone data files to tzdata release 2021a for DST law changes in Russia (Volgograd zone) and South Sudan, plus historical corrections for Australia, Bahamas, Belize, Bermuda, Ghana, Israel, Kenya, Nigeria, Palestine, Seychelles, and Vanuatu.
- Notably, the Australia/Currie zone has been corrected to the point where it is identical to Australia/Hobart.

更新時間：2021-02-12
更新細節：

更新時間：2021-02-12
更新細節：

更新時間：2021-02-12
更新細節：

更新時間：2021-02-12
更新細節：

What's new in this version:

- Fix failure to check per-column SELECT privileges in some join queries
- In some cases involving joins, the parser failed to record all the columns read by a query in the column-usage bitmaps that are used for permissions checking. Although the executor would still insist on some sort of SELECT privilege to run the query, this meant that a user having SELECT privilege on only one column of a table could nonetheless read all its columns through a suitably crafted query.
- A stored view that is subject to this problem will have incomplete column-usage bitmaps, and thus permissions will still not be enforced properly on the view after updating. In installations that depend on column-level permissions for security, it is recommended to CREATE OR REPLACE all user-defined views to cause them to be re-parsed.
- The PostgreSQL Project thanks Sven Klemm for reporting this problem. (CVE-2021-20229)
- Fix information leakage in constraint-violation error messages
- If an UPDATE command attempts to move a row to a different partition but finds that it violates some constraint on the new partition, and the columns in that partition are in different physical positions than in the parent table, the error message could reveal the contents of columns that the user does not have SELECT privilege on. (CVE-2021-3393)
- Fix incorrect detection of concurrent page splits while inserting into a GiST index
- Concurrent insertions could lead to a corrupt index with entries placed in the wrong pages. It's recommended to reindex any GiST index that's been subject to concurrent insertions.
- Fix CREATE INDEX CONCURRENTLY to wait for concurrent prepared transactions
- At the point where CREATE INDEX CONCURRENTLY waits for all concurrent transactions to complete so that it can see rows they inserted, it must also wait for all prepared transactions to complete, for the same reason. Its failure to do so meant that rows inserted by prepared transactions might be omitted from the new index, causing queries relying on the index to miss such rows. In installations that have enabled prepared transactions (max_prepared_transactions > 0), it's recommended to reindex any concurrently-built indexes in case this problem occurred when they were built.
- Avoid crash when trying to rescan an aggregation plan node that has both hashed and sorted grouping sets
- Fix possible incorrect query results when a hash aggregation node spills some tuples to disk
- It was possible for aggregation grouping values to be replaced by nulls when the tuples are read back in, leading to wrong answers.
- Fix edge case in incremental sort
- If the last tuple of a sort batch chanced to be the first tuple of the next group of already-sorted tuples, the code did the wrong thing. This could lead to “retrieved too many tuples in a bounded sort” error messages, or to silently-wrong sorting results.
- Avoid crash when a CALL or DO statement that performs a transaction rollback is executed via extended query protocol
- In PostgreSQL 13, this case reliably caused a null-pointer dereference. In earlier versions the bug seems to have no visible symptoms, but it's not quite clear that it could never cause a problem.
- Avoid unnecessary errors with BEFORE UPDATE triggers on partitioned tables
- A BEFORE UPDATE FOR EACH ROW trigger that modified the row in any way prevented UPDATE from moving the row to another partition when needed; but there is no longer any reason for this restriction.
- Fix partition pruning logic to handle asymmetric hash partition sets
- If a hash-partitioned table has unequally-sized partitions (that is, varying modulus values), or it lacks partitions for some remainder values, then the planner's pruning logic could mistakenly conclude that some partitions don't need to be scanned, leading to failure to find rows that the query should find.
- Avoid incorrect results when WHERE CURRENT OF is applied to a cursor whose plan contains a MergeAppend node
- This case is unsupported (in general, a cursor using ORDER BY is not guaranteed to be simply updatable); but the code previously did not reject it, and could silently give false matches.
- Fix crash when WHERE CURRENT OF is applied to a cursor whose plan contains a custom scan node
- Fix planner's mishandling of placeholders whose evaluation should be delayed by an outer join
- This occurs in particular with trivial subqueries containing lateral references to outer-join outputs. The mistake could result in a malformed plan. The known cases trigger a “failed to assign all NestLoopParams to plan nodes” error, but other symptoms may be possible.
- Fix planner's handling of placeholders during removal of useless RESULT RTEs
- This oversight could lead to “no relation entry for relid N” planner errors.
- Fix planner's handling of a placeholder that is computed at some join level and used only at that same level
- This oversight could lead to “failed to build any N-way joins” planner errors.
- Consider unsorted subpaths when planning a Gather Merge operation
- It's possible to use such a path by adding an explicit Sort node, and in some cases that gives rise to a superior plan.
- Do not consider ORDER BY expressions involving parallel-restricted functions or set-returning functions when trying to parallelize sorts
- Such cases cannot safely be pushed into worker processes, but the incremental sort feature accidentally made us consider them.
- Be more careful about whether index AMs support mark/restore
- This prevents errors about missing support functions in rare edge cases.
- Fix overestimate of the amount of shared memory needed for parallel queries
- Fix ALTER DEFAULT PRIVILEGES to handle duplicated arguments safely
- Duplicate role or schema names within the same command could lead to “tuple already updated by self” errors or unique-constraint violations.
- Flush ACL-related caches when pg_authid changes
- This change ensures that permissions-related decisions will promptly reflect the results of ALTER ROLE ... [NO] INHERIT.
- Fix failure to detect “snapshot too old” conditions in tables rewritten in the current transaction
- This is only a hazard when wal_level is set to minimal and the rewrite is performed by ALTER TABLE SET TABLESPACE.
- Fix spurious failure of CREATE PUBLICATION when applied to a table created or rewritten in the current transaction
- This is only a hazard when wal_level is set to minimal.
- Prevent misprocessing of ambiguous CREATE TABLE LIKE clauses
- A LIKE clause is re-examined after initial creation of the new table, to handle importation of indexes and such. It was possible for this re-examination to find a different table of the same name, causing unexpected behavior; one example is where the new table is a temporary table of the same name as the LIKE target.
- Rearrange order of operations in CREATE TABLE LIKE so that indexes are cloned before building foreign key constraints
- This fixes the case where a self-referential foreign key constraint declared in the outer CREATE TABLE depends on an index that's coming from the LIKE clause.
- Disallow CREATE STATISTICS on system catalogs
- Disallow converting an inheritance child table to a view
- Ensure that disk space allocated for a dropped relation is released promptly at commit
- Previously, if the dropped relation spanned multiple 1GB segments, only the first segment was truncated immediately. Other segments were simply unlinked, which doesn't authorize the kernel to release the storage so long as any other backends still have the files open.
- Prevent dropping a tablespace that is referenced by a partitioned relation, but is not used for any actual storage
- Previously this was allowed, but subsequent operations on the partitioned relation would fail.
- Fix progress reporting for CLUSTER
- Fix handling of backslash-escaped multibyte characters in COPY FROM
- A backslash followed by a multibyte character was not handled correctly. In some client character encodings, this could lead to misinterpreting part of a multibyte character as a field separator or end-of-copy-data marker.
- Avoid preallocating executor hash tables in EXPLAIN without ANALYZE
- Fix recently-introduced race condition in LISTEN/NOTIFY queue handling
- A newly-listening backend could attempt to read SLRU pages that were in process of being truncated, possibly causing an error.
- Allow the jsonb concatenation operator to handle all combinations of JSON data types
- We can concatenate two JSON objects or two JSON arrays. Handle other cases by wrapping non-array inputs in one-element arrays, then performing an array concatenation. Previously, some combinations of inputs followed this rule but others arbitrarily threw an error.
- Fix use of uninitialized value while parsing a * quantifier in a BRE-mode regular expression
- This error could cause the quantifier to act non-greedy, that is behave like a *? quantifier would do in full regular expressions.
- Fix numeric power() for the case where the exponent is exactly INT_MIN (-2147483648)
- Previously, a result with no significant digits was produced.
- Fix integer-overflow cases in substring() functions
- If the specified starting index and length overflow an integer when added together, substring() misbehaved, either throwing a bogus “negative substring length” error for a case that should succeed, or failing to complain that a negative length is negative (and instead returning the whole string, in most cases).
- Prevent possible data loss from incorrect detection of the wraparound point of an SLRU log
- The wraparound point typically falls in the middle of a page, which must be rounded off to a page boundary, and that was not done correctly. No issue could arise unless an installation had gotten to within one page of SLRU overflow, which is unlikely in a properly-functioning system. If this did happen, it would manifest in later “apparent wraparound” or “could not access status of transaction” errors.
- Fix WAL-reading logic to handle timeline switches correctly
- Previously, if WAL archiving is enabled, a standby could fail to follow a primary running on a newer timeline, with errors like “requested WAL segment has already been removed”.
- Fix memory leak in walsender processes while sending new snapshots for logical decoding
- Fix relation cache leak in walsender processes while sending row changes via the root of a partitioned relation during logical replication (Amit Langote, Mark Zhao)
- Fix walsender to accept additional commands after terminating replication
- Ensure detection of deadlocks between hot standby backends and the startup (WAL-application) process
- The startup process did not run the deadlock detection code, so that in situations where the startup process is last to join a circular wait situation, the deadlock might never be recognized.
- Fix possible failure to detect recovery conflicts while deleting an index entry that references a HOT chain
- The code failed to traverse the HOT chain and might thus compute a too-old XID horizon, which could lead to incorrect conflict processing in hot standby. The practical impact of this bug is limited; in most cases the correct XID horizon would be found anyway from nearby operations.
- Ensure that a nonempty value of krb_server_keyfile always overrides any setting of KRB5_KTNAME in the server's environment
- Previously, which setting took precedence depended on whether the client requests GSS encryption.
- In server log messages about failing to match connections to pg_hba.conf entries, include details about whether GSS encryption has been activated
- This is relevant data if hostgssenc or hostnogssenc entries exist.
- Fix assorted issues in server's support for GSS encryption
- Remove pointless restriction that only GSS authentication can be used on a GSS-encrypted connection. Add GSS encryption information to connection-authorized log messages. Include GSS-related space when computing the required size of shared memory (this omission could have caused problems with very high max_connections settings). Avoid possible infinite recursion when reporting an unrecoverable GSS encryption error.
- Ensure that unserviced requests for background workers are cleaned up when the postmaster begins a “smart” or “fast” shutdown sequence
- Previously, there was a race condition whereby a child process that had requested a background worker just before shutdown could wait indefinitely, preventing shutdown from completing.
- Fix portability problem in parsing of recovery_target_xid values
- The target XID is potentially 64 bits wide, but it was parsed with strtoul(), causing misbehavior on platforms where long is 32 bits (such as Windows).
- Avoid trying to use parallel index build in a standalone backend
- Allow index AMs to support included columns without necessarily supporting multiple key columns
- While taking a base backup, avoid executing any SHA256 code if a backup manifest is not needed
- When using OpenSSL operating in FIPS mode, SHA256 hashing is rejected, leading to an error. This change makes it possible to take a base backup on such a platform, so long as --no-manifest is specified.
- Avoid assertion failure during parallel aggregation of an aggregate with a non-strict deserialization function
- No such aggregate functions exist in core PostgreSQL, but some extensions such as PostGIS provide some. The mistake is harmless anyway in a non-assert build.
- Avoid assertion failure in pg_get_functiondef() when examining a function with a TRANSFORM option
- Fix data structure misallocation in PL/pgSQL's CALL statement
- A CALL in a PL/pgSQL procedure, to another procedure that has OUT parameters, would fail if the called procedure did a COMMIT or ROLLBACK.
- In libpq, do not skip trying SSL after GSS encryption
- If we successfully made a GSS-encrypted connection, but then failed during authentication, we would fall back to an unencrypted connection rather than next trying an SSL-encrypted connection. This could lead to unexpected connection failure, or to silently getting an unencrypted connection where an encrypted one is expected. Fortunately, GSS encryption could only succeed if both client and server hold valid tickets in the same Kerberos infrastructure. It seems unlikely for that to be true in an environment that requires SSL encryption instead.
- Make libpq's PQconndefaults() function report the correct default value for channel_binding
- In psql, re-allow including a password in a connection_string argument of a connect command
- This used to work, but a recent bug fix caused the password to be ignored (resulting in prompting for a password).
- In psql's d commands, don't truncate the display of column default values
- Formerly, they were arbitrarily truncated at 128 characters.
- Fix assorted bugs in psql's help command
- help with two argument words failed to find a command description using only the first word, for example help reset all should show the help for RESET but did not. Also, help often failed to invoke the pager when it should. It also leaked memory.
- Fix pg_dump's dumping of inherited generated columns
- The previous behavior resulted in (harmless) errors during restore.
- In pg_dump, ensure that the restore script runs ALTER PUBLICATION ADD TABLE commands as the owner of the publication, and similarly runs ALTER INDEX ATTACH PARTITION commands as the owner of the partitioned index
- Previously, these commands would be run by the role that started the restore script; which will usually work, but in corner cases that role might not have adequate permissions.
- Fix pg_dump to handle WITH GRANT OPTION in an extension's initial privileges
- If an extension's script creates an object and grants privileges on it with grant option, then later the user revokes such privileges, pg_dump would generate incorrect SQL for reproducing the situation. (Few if any extensions do this today.)
- In pg_rewind, ensure that all WAL is accounted for when rewinding a standby server
- In pgbench, disallow a digit as the first character of a variable name
- This prevents trying to substitute variables into timestamp literal values, which may contain strings like 12:34.
- Report the correct database name in connection failure error messages from some client programs
- If the database name was defaulted rather than given on the command line, pg_dumpall, pgbench, oid2name, and vacuumlo would produce misleading error messages after a connection failure.
- Fix memory leak in contrib/auto_explain
- Memory consumed while producing the EXPLAIN output was not freed until the end of the current transaction (for a top-level statement) or the end of the surrounding statement (for a nested statement). This was particularly a problem with log_nested_statements enabled.
- In contrib/postgres_fdw, avoid leaking open connections to remote servers when a user mapping or foreign server object is dropped
- Open connections that depend on a dropped user mapping or foreign server can no longer be referenced, but formerly they were kept around anyway for the duration of the local session.
- Fix faulty assertion in contrib/postgres_fdw
- In contrib/pgcrypto, check for error returns from OpenSSL's EVP functions
- We do not really expect errors here, but this change silences warnings from static analysis tools.
- Make contrib/pg_prewarm more robust when the cluster is shut down before prewarming is complete
- Previously, autoprewarm would rewrite its status file with only the block numbers that it had managed to load so far, thus perhaps largely disabling the prewarm functionality in the next startup. Instead, suppress status file updates until the initial loading pass is complete.
- In contrib/pg_trgm's GiST index support, avoid crash in the rare case that picksplit is called on exactly two index items
- Fix miscalculation of timeouts in contrib/pg_prewarm and contrib/postgres_fdw
- The main loop in contrib/pg_prewarm's autoprewarm parent process underestimated its desired sleep time by a factor of 1000, causing it to consume much more CPU than intended. When waiting for a result from a remote server, contrib/postgres_fdw overestimated the desired timeout by a factor of 1000 (though this error had been mitigated by imposing a clamp to 60 seconds).
- Both of these errors stemmed from incorrectly converting seconds-and-microseconds to milliseconds. Introduce a new API TimestampDifferenceMilliseconds() to make it easier to get this right in the future.
- Improve configure's heuristics for selecting PG_SYSROOT on macOS
- The new method is more likely to produce desirable results when Xcode is newer than the underlying operating system. Choosing a sysroot that does not match the OS version may result in nonfunctional executables.
- While building on macOS, specify -isysroot in link steps as well as compile steps
- This likewise improves the results when Xcode is out of sync with the operating system.
- Fix JIT compilation to be compatible with LLVM 11 and LLVM 12
- Fix potential mishandling of references to boolean variables in JIT expression compilation
- No field reports attributable to this have been seen, but it seems likely that it could cause problems on some architectures.
- Fix compile failure with ICU 68 and later
- Avoid memcpy() with a NULL source pointer and zero count during partitioned index creation
- While such a call is not known to cause problems in itself, some compilers assume that the arguments of memcpy() are never NULL, which could result in incorrect optimization of nearby code.
- Update time zone data files to tzdata release 2021a for DST law changes in Russia (Volgograd zone) and South Sudan, plus historical corrections for Australia, Bahamas, Belize, Bermuda, Ghana, Israel, Kenya, Nigeria, Palestine, Seychelles, and Vanuatu.
- Notably, the Australia/Currie zone has been corrected to the point where it is identical to Australia/Hobart.

更新時間：2021-02-12
更新細節：

What's new in this version:

Visual Studio Code 1.53.2 (64-bit)
Fixed:
- TS Server fatal error: Cannot read property 'indexOf' of undefined
- <<RENDER ERROR>> in all files
- Minimap keeps disappearing
- Fresh install won't open any windows or allow me to open any windows
- First call to activeDebugConsole.appendLine() while debugging JavaScript doesn't appear in the debug console
- Cannot unset StatusBarItem background from errorBackground
- tasks.json npm script does not work with arguments since 1.53
- v1.53 creates debug.log automatically
- The default extension for untitled files is not .txt
- Emmet suggestions bug in SASS files
- VSCode emmet SASS snippets
- IME ON at Alt+` key, Focus ALT Menu


Visual Studio Code 1.53.1 (64-bit)
Security issues:
- Bundle TypeScript 4.1.4
- Dragging files from explorer to terminal may execute a command
- Pick up new distro version and bump version


Visual Studio Code 1.53.0 (64-bit)
- Wrap tabs - Wrap editor tabs in the workbench instead of having a scrollbar
- Configure tab decorations - Add editor tab status decorations
- Customize search mode - Use the Search view or open a new Search editor
- JavaScript debugging - Support for conditional exception breakpoints and Node.js worker_threads
- Notebook UX updates - Outline view for Notebook cells, and breadcrumbs for improved navigation
- Markdown preview image auto update - Preview automatically updates when images change
- Emmet improvements - Faster performance and supporting the latest features
- Extension guidelines - Documented best practices for extension authors
- Remote Development video series - Learn to create and configure container-based environments


Visual Studio Code 1.52.1 (64-bit)
- November 2020 Recovery Endgame
- Check for all possible localhost string when checking if a tunnel already exists
- Can not set breakpoint in PHP files
- notebook status bar icon colors missing


Visual Studio Code 1.52.0 (64-bit)
- Word wrap in diff editor - Both inline and side-by-side views now support word wrapping
- New extension bisect feature - Troubleshoot which extensions are causing issues in VS Code
- Keyboard shortcuts editor improvements - Create a keybinding from the Command Palette
- Undo file operations in Explorer - Undo or redo file operations in the Explorer
- New Git commands and settings - Optimize your Version Control experience with new capabilities
- Preview editor improvements - Turn off preview editors altogether, and try new interaction models
- Sticky tab stops for spaces - Improved experience when indenting with spaces
- Improved word-based suggestions - Display word-based suggestions from other open files
- Terminal configuration support - Modify terminal settings from the terminal dropdown menu
- New Remote Development resources - Check out the new video and Learn module


Visual Studio Code 1.51.1 (64-bit)
- "Reveal In Side Bar" does not work if the file is opened from external apps
- New ThemeIcon color in tree views can pollute other nodes


Visual Studio Code 1.51.0 (64-bit)
New:
- unassigned Focus Left Editor Group (do not wrap around) workbench.action.focusLeftGroupWithoutWrap
- unassigned Focus Right Editor Group (do not wrap around) workbench.action.focusRightGroupWithoutWrap
- unassigned Focus Above Editor Group (do not wrap around) workbench.action.focusAboveGroupWithoutWrap
- unassigned Focus Below Editor Group (do not wrap around) workbench.action.focusBelowGroupWithoutWrap
- unassigned Focus Activity Bar workbench.action.focusActivityBar

Fixed:
- Windows: when deleting a folder with files that are in use, then there is no error message shown
- Should maintain row focus after deleting a file
- User input variables not working for launch configuration in multi-root workspace
- Moving a file should load the model directly with the contents it had before
- Extensions with a onDebugDynamicConfigurations are eagerly activated at startup in v1.50
- Send vscode.workspace.onWillCreateFiles/onDidCreateFiles events for folders
- Debug hover moves while expanding/collapsing


Visual Studio Code 1.50.1 (64-bit)
- relativeFileDirname` gives empty string when the Dirname equals to current working directory
- Multiple prompt to grant access to login keychain


Visual Studio Code 1.50.0 (64-bit)
- Accessible settings editor - Interact with the settings list like any other list in VS Code
- Pinned tabs improvements - Resize pinned tabs, unpin with one click, and more
- Linux ARM builds - VS Code is now available for both Linux ARMv7 and ARM64
- Improved debugging experience - Improved hover and filtering in debug console
- New JS debugger features - Toggle auto attach flows and see performance in real-time
- Panel layout improvements - New panel maximization settings and bottom panel size
- Webview Views support - Build extensions with webview views in the sidebar and panel
- Updated "Create a Dev Container" tutorial - Get started with Development Containers


Visual Studio Code 1.49.3 (64-bit)
- August Recovery Endgame 3
- (Assumed) Fix for CVE-2020-16881 can be bypassed


Visual Studio Code 1.49.2 (64-bit)
- Format modified text - Limit formatting to just the code you've changed
- Change casing on Search and Replace - Change text casing during global Search and Replace
- Source Control repositories view - Display pending changes per repository
- Filter Debug Console output - Quickly filter and find debugging output
- Improved JS debugger Auto Attach - "Smart" Auto Attach to Node.js scripts or test runners
- TypeScript optional chaining refactoring - Convert multiple checks to a concise optional chain
- JSDoc @deprecated tag support - IntelliSense clearly shows APIs marked as deprecated
- Notebook UX updates - Cell Status bar contributions, enhanced notebook diff editor


Visual Studio Code 1.49.1 (64-bit)
The update addresses these issues:
- August 2020 Recovery Endgame
- Completions which use spaces are broken after updating from July to August version
- EPIPE write failure while debugging after upgrading to 1.49
- proxy authentication does not work on 1.49


Visual Studio Code 1.49.0 (64-bit)
There are a number of updates in this version that we hope you will like, some of the key highlights include:
- Format modified text - Limit formatting to just the code you've changed
- Change casing on Search and Replace - Change text casing during global Search and Replace
- Source Control repositories view - Display pending changes per repository
- Filter Debug Console output - Quickly filter and find debugging output
- Improved JS debugger Auto Attach - "Smart" Auto Attach to Node.js scripts or test runners
- TypeScript optional chaining refactoring - Convert multiple checks to a concise optional chain
- JSDoc @deprecated tag support - IntelliSense clearly shows APIs marked as deprecated
- Notebook UX updates - Cell Status bar contributions, enhanced notebook diff editor


Visual Studio Code 1.48.2 (64-bit)
- Settings Sync to Stable - Settings Sync is now available for preview in stable
- Updated Extensions view menu - Simplified menu with additional filtering options
- New Git View submenus - Refactored overflow menu for Git in the Source Control view
- Updated in-browser debugging - Debug in the browser without writing a launch configuration
- Publish a public repository - Choose whether to publish to a public or private GitHub repository
- Notebook UX updates - New Cell menu, enhanced drag and drop
- New Remote Container topics - Learn how to attach to a container and create a new dev container
- Java lightweight mode - Start working with your Java source files more quickl


Visual Studio Code 1.48.1 (64-bit)
The update addresses these issues:
- Correct wording of the WSL recommendation
- July Recovery Endgame
- Right Click on Extension Search > Peek causes freeze
- Run Build Task List Not Sorting
- Cannot overwrite read only files anymore
- [v1.48] [Breaking] Cannot authenticate proxies
- There is no way to show the NPM scripts explorer when there is no top level package.json
- "IPersistFile::Save failed" during installation of VS Code Insiders
- Error while starting Sync: d is not iterable
- Saving untitled file always defaults to .txt


Visual Studio Code 1.48.0 (64-bit)
- Settings Sync to Stable: settings Sync is now available for preview in stable
- Updated Extensions view menu: simplified menu with additional filtering options
- New Git View submenus: refactored overflow menu for Git in the Source Control view
- Updated in-browser debugging: debug in the browser without writing a launch configuration
- Publish a public repository: choose whether to publish to a public or private GitHub repository
- Notebook UX updates: new Cell menu, enhanced drag and drop
- New Remote Container topics: learn how to attach to a container and create a new dev container
- Java lightweight mode: start working with your Java source files more quickly


Visual Studio Code 1.47.3 (64-bit)
Fixed:
- June 2020 Recovery 3 Engame
- ERR_INVALID_ARG_TYPE when testing extension on 1.47.1
- Uninstall hook not executing


Visual Studio Code 1.47.2 (64-bit)
- June 2020 Recovery 2 Engame
- Menus: Dropdown menu gets tiny when opened near the edge of the workbench
- SCM: View becomes empty, with errors in dev tools
- Snippets | Clipboard is not working
- "Proposed API is only available..." error in v1.47
- "Duplicate Workspace in New Window" just creates new window and opens workspace.json file
- Output channel Log (Window) does not appear until window reload for the first time
- Creating files will add 2 times BOM (UTF-8, 16)
- Reading from stdin via tmp file and pipe raise an exception
- Extensions issues after update to vscode 1.47.0
- [node-debugger] Debugger spams "Could not read sourcemaps" messages
- Node version detection causes issues with old Electron versions + Node >=12 on the PATH
- Double pasting in a webview with latest insiders
- Can't debug node application


Visual Studio Code 1.47.1 (64-bit)
- Accessibility improvements - New screen reader capabilities
- Windows ARM builds - Windows on ARM is now available in stable
- New JavaScript debugger - Debug in the terminal, profiling support
- Source Control unified view - All repositories displayed in a single view
- View and sort pending changes - View files as a tree or list, sort by name, path, or status
- Edit complex settings - Edit object settings from the Settings editor
- New HexEditor extension - Edit files in hexadecimal format from within VS Code
- Notebook UI updates - Improved UX and undo/redo support
- Remote Development tutorials - Learn to develop over SSH, inside Containers, and in WSL
- Java Pack Installer for macOS - Get set up to develop in Java with VS Code on macOS


Visual Studio Code 1.47.0 (64-bit)
- Accessibility improvements - New screen reader capabilities
- Windows ARM builds - Windows on ARM is now available in stable
- New JavaScript debugger - Debug in the terminal, profiling support
- Source Control unified view - All repositories displayed in a single view
- View and sort pending changes - View files as a tree or list, sort by name, path, or status
- Edit complex settings - Edit object settings from the Settings editor
- New HexEditor extension - Edit files in hexadecimal format from within VS Code
- Notebook UI updates - Improved UX and undo/redo support
- Remote Development tutorials - Learn to develop over SSH, inside Containers, and in WSL
- Java Pack Installer for macOS - Get set up to develop in Java with VS Code on macOS


Visual Studio Code 1.46.1 (64-bit)
- Accessibility improvements - Status bar navigation, easier keyboard text selection
- Flexible view and panel layout - Move and group views in the Side Bar and Panel
- Pinned editor tabs - Pin editors in the title bar to keep frequently used files handy
- Add GitHub remotes - Add GitHub remotes to your local repository
- Automatic debugger configuration - Save and modify generated debug configurations
- JavaScript CommonJS auto imports - Auto imports will now use require for CommonJS modules
- JS/TS refactorings preserve newlines - Formatting is preserved during refactoring operations
- Settings Sync preview - New Synced Machines and Data views to manage your preferences
- GitHub Issue Notebooks - Run GitHub issue queries and display results in a custom Notebook
- Windows ARM64 support - New VS Code Insiders ARM64 builds are available
- VS Code at Build 2020 - Talks on Tips&Tricks, Remote Development, and The History of VS Code


Visual Studio Code 1.46.0 (64-bit)
- Accessibility improvements - Status bar navigation, easier keyboard text selection
- Flexible view and panel layout - Move and group views in the Side Bar and Panel
- Pinned editor tabs - Pin editors in the title bar to keep frequently used files handy
- Add GitHub remotes - Add GitHub remotes to your local repository
- Automatic debugger configuration - Save and modify generated debug configurations
- JavaScript CommonJS auto imports - Auto imports will now use require for CommonJS modules
- JS/TS refactorings preserve newlines - Formatting is preserved during refactoring operations
- Settings Sync preview - New Synced Machines and Data views to manage your preferences
- GitHub Issue Notebooks - Run GitHub issue queries and display results in a custom Notebook
- Windows ARM64 support - New VS Code Insiders ARM64 builds are available
- VS Code at Build 2020 - Talks on Tips&Tricks, Remote Development, and The History of VS Code


Visual Studio Code 1.45.1 (64-bit)
- Accessibility improvements - Focus commands to navigate the workbench, status bar accessibility
- Switch editor tabs via mouse wheel - Quickly switch files in the editor using your mouse wheel
- Faster syntax highlighting - Programming language colorization is up to 3 times faster
- Custom semantic colors - Change semantic token colors through your user settings
- GitHub authentication support - Automatic GitHub authentication for GitHub repositories
- GitHub Issues integration - Inline hovers and suggestions for GitHub issues and users
- Remote Development - Container configuration recommendations, WSL 2 support
- JavaScript debugger preview - CPU profiling, improved Auto Attach to Node.js processes
- New Docker Compose topic - Learn how to use Docker Compose to work with multiple containers


Visual Studio Code 1.45.0 (64-bit)
- Accessibility improvements: focus commands to navigate the workbench, status bar accessibility
- Switch editor tabs via mouse wheel: quickly switch files in the editor using your mouse wheel
- Faster syntax highlighting:programming language colorization is up to 3 times faster
- Custom semantic colors: change semantic token colors through your user settings
- GitHub authentication support: automatic GitHub authentication for GitHub repositories
- GitHub Issues integration: inline hovers and suggestions for GitHub issues and users
- Remote Development: container configuration recommendations, WSL 2 support
- JavaScript debugger preview: CPU profiling, improved Auto Attach to Node.js processes
- New Docker Compose topic: learn how to use Docker Compose to work with multiple containers


Visual Studio Code 1.44.2 (64-bit)
The update addresses these issues:
- Show notification when extensionHostProcess.js is missing on disk
- Can't search in workspace that includes folder using a FileSystemProvider
- Git on network drive broken after upgrade to 1.44.0
- Can't select recently visited file using arrow keys
- Using spaces in symbol (editor, workspace) picker can confuse results
- Action "merge all windows" gone after update to 1.44
- Possible regression: As of 1.44 cannot open multiple files from "Go to file..." menu
- '${workspaceFolder}' can not be resolved in a multi folder workspace
- Editor stays blurred when moving panels


Visual Studio Code 1.44.1 (64-bit)
- Change log not available for this version


Visual Studio Code 1.44.0 (32-bit)
- Accessibility improvements - Easier diff view navigation, clearer role designations for UI controls
- Timeline view - See time-series events like Git commit history from within VS Code
- Better Quick Open for files - Navigate smoothly from files to symbols, filter files by folder name
- Extension Pack display - Quickly see what is bundled in an Extension Pack
- Persisted Undo/Redo stack - Undo/Redo stack preserved for reopened files
- Remote Development - Directly check out Pull Requests into containers, support for Kubernetes
- Settings Sync preview - Settings Sync now lets you share snippets and UI state across machines
- New Python tutorials - Tutorials for creating Python containers and building Data Science models


Visual Studio Code 1.43.2 (64-bit)
The update addresses these issues:
- February 2020 Recovery 2 Endgame
- The specified task cannot be tracked
- [Meta] Crash with webview after updated to 1.43.0


Visual Studio Code 1.43.1 (64-bit)
- February 2020 Recovery Endgame
- Prelaunch tasks without a command don't work the second time
- Semantic highlighting improvements for 1.43.1
- [web] Welcome views: links trigger unload
- [semantic highlighting] functions in josef.rouge-theme get wrong color
- [less] color info missing
- VSCode since 1.43 freezes on deleting line in c++ file
- When relaunching for 1.43.0 update, vscode tries to open ~80 old workspaces


Visual Studio Code 1.43.0 (64-bit)
- Search Editors - Search and save your global search results in a full-sized editor
- Draggable sash corners - Easily change the editor layout by dragging sash corners
- Linux screen reader support - VS Code now supports the Orca screen reader
- Minimap sizing options - New options to fit or fill the minimap vertical layout
- Column selection mode - Column mode toggle lets you quickly select blocks of text
- Display whitespace on selection - Render whitespace characters only in selected text
- Convert to template string - Convert concatenations to JavaScript/TypeScript template strings
- JS/TS Call Hierarchy view - Review all calls to or from a function and drill into callers of callers
- Remote Development - Support for Windows and macOS SSH hosts, SSH connection sharing
- Settings Sync preview - Settings Sync lets you share settings and keybindings across machines


Visual Studio Code 1.42.1 (64-bit)
- Rename preview: see pending renames in a diff view and easily accept or reject changes
- Open editors limit: set the maximum number of editors open at one time
- Panel placement: move the panel (Output, Terminal) to the left, right, or below the editor
- Folded code highlighting: quickly find folded regions with new background highlight
- Debug Console improvements: syntax highlighting, bracket matching, input history
- Define global tasks: per user tasks can be used across all your folders and workspaces
- Java extension updates: Java support for Data Breakpoints and Call Hierarchy view
- Remote Development: new Forwarded Ports view for mapping SSH and Containers ports
- New Containers tutorials: learn how to create and deploy Docker containers
- Preview features: first looks at the Timeline view, Search editor, semantic highlighting, and more


Visual Studio Code 1.42.0 (64-bit)
- Rename preview: see pending renames in a diff view and easily accept or reject changes
- Open editors limit: set the maximum number of editors open at one time
- Panel placement: move the panel (Output, Terminal) to the left, right, or below the editor
- Folded code highlighting: quickly find folded regions with new background highlight
- Debug Console improvements: syntax highlighting, bracket matching, input history
- Define global tasks: per user tasks can be used across all your folders and workspaces
- Java extension updates: Java support for Data Breakpoints and Call Hierarchy view
- Remote Development: new Forwarded Ports view for mapping SSH and Containers ports
- New Containers tutorials: learn how to create and deploy Docker containers
- Preview features: first looks at the Timeline view, Search editor, semantic highlighting, and more


Visual Studio Code 1.41.1 (64-bit)
- Compact folders in Explorer: Single child folders collapsed by default
- Edit left side of diff views: You can now edit both files in a difference view
- Update search results while typing: Global search results update while you type
- Problems panel improvements: Filter by problem type and limit output to the active file
- Minimap highlights errors and content changes: Quickly locate problems and changes in your file
- Terminal minimum contrast ratio: Set preferred contrast ratio for increased visibility
- HTML mirror cursor in tags: Automatic multi-cursor in matching HTML tags
- Optional chaining in JS/TS: Use the ?. operator to simplify working with nested structures
- Extract interface refactoring: Quickly extract an inline type to a TypeScript interface
- Remote - Containers extension: Better support for opening repositories in Docker containers
- Visual Studio Online: Create and connect to cloud-based development environments


Visual Studio Code 1.41.0 (64-bit)
- Compact folders in Explorer: Single child folders collapsed by default
- Edit left side of diff views: You can now edit both files in a difference view
- Update search results while typing: Global search results update while you type
- Problems panel improvements: Filter by problem type and limit output to the active file
- Minimap highlights errors and content changes: Quickly locate problems and changes in your file
- Terminal minimum contrast ratio: Set preferred contrast ratio for increased visibility
- HTML mirror cursor in tags: Automatic multi-cursor in matching HTML tags
- Optional chaining in JS/TS: Use the ?. operator to simplify working with nested structures
- Extract interface refactoring: Quickly extract an inline type to a TypeScript interface
- Remote - Containers extension: Better support for opening repositories in Docker containers
- Visual Studio Online: Create and connect to cloud-based development environments


Visual Studio Code 1.40.2 (64-bit)
The update addresses these issues:
- Insider build always starts language server with debug options
- Occluded windows just went blank
- Port 9229 in use by VS Code
- "Save Workspace As..." does not save with correct extension
- Extension Host broken
- Touch bar mac disabled on focus file
- Child_process results in ENOMEM error with empty options.env
- MacOS: File > Open no longer adds files to recently opened
- 1.40.0 has rendering lag and flickers when minimize/maximize window with custom title
- Leaving Full Screen or Zen Mode leads to wrong window dimensions
- Maximize button not working properly with auto-hide taskbar enabled
- WebViewPanel created with preserveFocus: true suffers from a focus problem


Visual Studio Code 1.40.1 (64-bit)
- Change log not available for this version


Visual Studio Code 1.39.2 (64-bit)
Fixed:
- Error icons not showing up properly
- Some Octicons not working in quick pick
- Blank screen with a reinstalled 1.39.1
- VSCode starts with disabled extensions
- Webview.asWebviewUri not working in Remote
- SCM: SVN extension decorations are misaligned
- Command line error - "Option 'proxy-server' is unknown. Ignoring."
- Enable the bracket pair colorizer V2 extension for remote
- Mac touchbar debug not working
- Invisible dirty icon
- vscode://file/... does not work any longer
- Source control showing nothing
- Backslash in folder name still not handled correctly by flattened tree view


Visual Studio Code 1.39.1 (64-bit)
- Change log not available for this version


Visual Studio Code 1.39.0 (64-bit)
- Text selections displayed in minimap: see selection regions in the minimap overview
- Toggle region folding keyboard shortcut: quickly expand and collapse regions with Toggle Fold
- Source Control tree view: display pending changes in either a list or new tree view
- Open terminal in custom working directory: add keyboard shortcuts for specific folders
- HTML ARIA attribute reference links: links to ARIA documentation directly from IntelliSense
- CSS property completions include semicolons: semicolons added as you enter CSS properties
- CSS color variables preview: color variable completions display color swatch
- Improved column breakpoint UI: view possible inline breakpoints directly in your source code
- Inline debug actions in CALL STACK view: stay in context with debug actions on hover
- Remote Explorer updates: explorer now displays WSL distros and repository containers


Visual Studio Code 1.38.1 (64-bit)
The update addresses these issues:
- code.sh: remove wsl2 workaround
- Cannot insert a < div >, automatically corrects to < /div >
- Markdown Hover images broken
- statusbar border no longer appears [statusbar.border]
- Gap in right side of window
- Grouping quick open entries is broken


Visual Studio Code 1.38.0 (64-bit)
- Preserve case for global search and replace - Keep letter casing across multi-file search/replace
- Settings editor string array validation - Checks min, max, enum values, and glob patterns
- Adjust cursor surrounding lines - Keep your cursor centered in the editor
- Copy and revert in the diff editor - Easily copy or restore deleted content
- Go to Line supports negative line numbers - Quickly jump to the end of a file
- MDN Reference link for HTML and CSS - Links to MDN documentation directly from IntelliSense
- Add missing await Quick Fix - Find overlooked awaits in asynchronous code
- Debugging data breakpoints - Debugger breaks when tracked values change
- VS Code icon repository - Official product icons available for extension authors
- Alpine Linux distro support - Both for the Remote WSL and Containers extensions


Visual Studio Code 1.37.1 (64-bit)
- Recovery build has wrong icon for release notes
- July 2019 Recovery Release Endgame
- Pasting in a Windows->Linux remote window adds additional new line characters
- 1.37 breaks the fsprovider-sample extension
- Broken vscode.ProcessExecution in Tasks API in v1.37
- Alt+click in terminal resets scroll position and prevents click-on-link
- Certain C++ files completely freeze VSCode
- 1.37 Explorer not showing any files or folders
- Diagnostics show empty parentheses if no code specified for error (regression)


Visual Studio Code 1.37.0 (64-bit)
- Full product icon refresh: new modern icons across all of VS Code
- Edit string arrays in the Settings UI: add to string arrays directly from the Settings editor
- Reveal search result in File Explorer: quickly jump to file locations in the File Explorer
- Show whitespace in selection: see whitespace characters just for selected text
- Find and Replace preserves casing: replace text without losing letter casing
- Terminal search UX improvements: more intuitive bottom-up search order for the terminal
- Better SCSS @import navigation: VS Code now checks more locations for SCSS files
- Remote Development tutorials: new step-by-step tutorials for working over SSH and in WSL


Visual Studio Code 1.36.1 (64-bit)
- Hide/show status bar items: only display your preferred status bar items
- Indent guides in explorers: clearly highlights your project's folder structure
- Better terminal shell selector: easily select the default shell to use in the Integrated Terminal
- Sequential task execution: control the order of task and subtask execution
- Jump to cursor debugging: skip code execution as you jump to a new location
- Disable debug console word wrap: lets you keep debugging output to one line
- JavaScript/TypeScript nightly builds: new extension integrates JS/TS nightly builds
- New Java installer: installs VS Code, the Java extension pack, and required Java dependencies
- Remote Development (Preview) improvements: save to local file system, drag and drop files to remotes, and more


Visual Studio Code 1.36.0 (64-bit)
- Hide/show status bar items: only display your preferred status bar items
- Indent guides in explorers: clearly highlights your project's folder structure
- Better terminal shell selector: easily select the default shell to use in the Integrated Terminal
- Sequential task execution: control the order of task and subtask execution
- Jump to cursor debugging: skip code execution as you jump to a new location
- Disable debug console word wrap: lets you keep debugging output to one line
- JavaScript/TypeScript nightly builds: new extension integrates JS/TS nightly builds
- New Java installer: installs VS Code, the Java extension pack, and required Java dependencies
- Remote Development (Preview) improvements: save to local file system, drag and drop files to remotes, and more


Visual Studio Code 1.35.1 (64-bit)
Notable improvements:
- Collapse All list and tree command with Ctrl+Left keyboard shortcut
- The history of the References view can now be cleared
- When running the Format With... command, the default formatter is now pre-selected
- When debugging is paused on a line, the whole line is read out by the screen reader
- Multiple item paste in the Explorer is run in parallel for improved performance
- The Open Folder button in an empty File Explorer is scoped to folder even on macOS

Notable fixes:
- Potential data loss for files that changed on disk meanwhile after a backup was made
- Preserve picked language for files across restarts
- Completion providers with resolve methods leak memory
- URI: Should invalidate cached _fsPath when crossing platforms
- Make workbench.dialogs.useSimplified a real setting
- Clicking anywhere on the "debug console" pane should "focus" on input box
- Breakpoint lines are not correct when saving the source file after modifying the file
- Typescript task detection is now cross-platform


Visual Studio Code 1.35.0 (64-bit)
- Updated Visual Studio Code icon: The product logo got a refresh. We hope you like it
- Go to Definition improvements: Faster navigation through multiple definitions
- Breadcrumb navigation displayed by default: Quickly go to files and symbols via breadcrumbs
- Smart selection for JavaScript/TypeScript: Expand text selection based on language semantics
- Extract to type alias TypeScript refactoring: Extract part type into its own type alias
- Integrated terminal supports true color: Correctly renders true color (24-bit) escape sequences
- Better merge conflict display: See merge conflict changes within surrounding source code
- Collapse All command for lists and explorers: One of many small but handy improvements
- Remote Development (Preview) available in Stable: You can now use the Remote Development extensions in Stable


Visual Studio Code 1.34.0 (64-bit)

Editor:
Stable CodeLens:
- VS Code now optimistically caches CodeLens locations and restores them immediately after switching editors. This fixes an issue where CodeLens lines would shift slightly when switching between editors

Languages:
Lower rank for CSS property values with vendor prefix:
- CSS property values prefixed with dash '-' (such as -moz-grid or -ms-grid), now come after grid in auto completion

Debugging:
- debug.showSubSessionsInToolBar
- We have introduced the setting debug.showSubSessionsInToolBar which controls whether the debug sub-sessions are shown in the debug tool bar. When this setting is false, the stop command on a sub-session will also stop the parent session. This setting default is false

Tasks:
Terminate all tasks:
- The Tasks: Terminate Task command has a new option to terminal all tasks if there are multiple tasks running. If this is an action you do often, you can create a keyboard shortcut for the command with the terminateAll argument

Automatically show Problems panel:
- The new revealProblems task property allows you to automatically show the Problems panel. The property values are always, never, and onProblem

Contributions to extensions:
Preview: Remote Development:
- Note: The Remote Development extensions require Visual Studio Code Insiders
- Visual Studio Code Remote Development allows you to use a container, remote machine, or the Windows Subsystem for Linux (WSL) as a full-featured development environment
- The extensions in the Remote Development extension pack run in the context of the remote workspace while VS Code feels like it does when you run locally

Vetur:
- The Vetur extension now offers semantic diagnostics, hover information, jump to definition, and find references for the JavaScript expression inside Vue's template interpolation region
- Other improvements include reduced memory usage and import path completion. You can learn more about them in the Vetur changelog

Extension authoring:
Multi-extension debugging:
- In this milestone, we've added support for debugging more than one extension at a time. This is useful if you are developing a set of tightly coupled or interdependent extensions
- Previously this feature was only surfaced via the command-line interface of VS Code, now the argument --extensionDevelopmentPath can be specified more than once. Typically --extensionDevelopmentPath is used in the launch configuration of an extension. When developing more than one extension, we recommend combining the individual extension projects into a multi-folder workspace and create a new launch configuration (stored in the workspace .code-workspace file) that uses multiple --extensionDevelopmentPath arguments for the individual extensions
- Please note that in this release, it is not possible to create a preLaunchTask that builds both extensions by combining the preLaunchTasks of the individual extension projects

Command links in notifications:
- It was always possible to include links in notification messages via the syntax [link name](http://link), but this only worked for links that open in a browser. Now you can also invoke a command from a link with the syntax [link name](command:). The command with the provided identifier will be triggered when the user clicks the link

Links in notifications allow for title:
- You can now add a title to links in notifications that will be shown when the user hovers over the link. The syntax is [link name](link "")

Proposed extension APIs:
Every milestone comes with new proposed APIs and extension authors can try them out. As always we are keen on your feedback. This is what you have to do to try out a proposed API:
- You must use Insiders because proposed APIs change frequently
- You must have this line in the package.json file of your extension: "enableProposedApi": true
- Copy the latest version of the vscode.proposed.d.ts file into your project
- Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions

vscode.workspace.workspaceFile:
- There is a new workspace property returning the location of the workspace file. For example: file:///Users/name/Development/myProject.code-workspace or untitled:1555503116870 for a workspace that is untitled and not yet saved

Depending on the workspace that is opened, the value will be:
- undefined when no workspace or a single folder is opened.
- The path of the workspace file as Uri
- If the workspace is untitled, the returned URI will use the untitled: scheme

One use of the workspace file location is to call the vscode.openFolder command to open the workspace again after it has been closed:
- vscode.commands.executeCommand('vscode.openFolder', uriOfWorkspace);
- Note: It is not recommended using the workspace.workspaceFile location to write configuration data directly into the file. You can use workspace.getConfiguration().update() which will work both when a single folder is opened as well as an untitled or saved workspace
- Machine-specific settings
- If you have settings that allow users to customize an executable path and if these paths need to be scoped to the machine they are running on, you can now classify such settings as machine scoped. Extension authors set the scope property when contributing to the configuration extension point. Machine-specific settings can only be configured for User settings

Engineering:
Rewritten filesystem provider for local files:
- Extensions ave been able to provide their own filesystem implementations for custom resources (read more here). However, VS Code's own implementation for local files was not implemented with the same extension APIs. This resulted in subtle differences when dealing with local file resources compared to resources coming from extensions. Over the last two milestones, we rewrote our local file system provider to use the extension APIs for consistency

New documentation:
Python Azure Functions:
- There is a new Deploy Python to Azure Functions tutorial that describes how to create and deploy Python serverless Azure Functions

Miscellaneous:
Language Server Protocol:
The Language Server Protocol has proposed support for the following new features:
- Selection ranges: to compute selection ranges for an array of positions. Sent from client to server
- Call hierarchy: to compute a call hierarchy for a given symbol. Sent from client to server
- Progress: to initiate progress reporting from the server. Sent from server to client
- The new features are available in the next versions of the vscode-languageclient and vscode-languageserver npm modules

Notable fixes:
- Explorer Respects Trash Capability from FileSystemProvider
- Call Stack "Paused On Breakpoint" UI not visible for long thread names
- Terminal window crashes in Mac OS
- Debug Console render newlines unnecessary
- Scrolling in debug window is behaving strange
- Error revealing files in the explorer
- Report issue’ button on ‘Running extensions’ causes tens of duplicate issues


Visual Studio Code 1.33.1 (64-bit)

Fixed:
- Evironment variables not expanding in tasks
- New and delete keywords no longer highlighted in C++ file
- Formatter Settings UI shows strange default
- Adopt TypeScript 3.4.3
- Unable to select first formatter in picker
- "name" property of OutputChannel has gone
- Recent update of INSIDERS Edition made COG Wheel completely disappear
- Prettier formatting causes document to jump with insiders


Visual Studio Code 1.33.0 (64-bit)
- Easy Display Language selection: Quick Pick to choose between installed locales
- Configurable IntelliSense display: Filter out elements like keywords or remove displayed icons
- Choose default formatter: Set default document formatter by project and language
- Go to Definition locations: Open Peek view and/or navigate to primary location
- Convert to destructured parameters: New TS refactoring to use named parameter objects
- Debugging support for subsessions: See subprocesses displayed under main debug session
- Launch URI with debug session: Automatically open a browser when debugging web server code
- Install missing extension dependencies: Detect and offer to install missing dependencies
- "Remote Debugging for Node.js" topic: Learn how to attach to Node.js apps running on Azure
- Workbench: Improved Source Control view, easier list navigation with screen readers
- Integrated Terminal: ConPTY on by default on Windows, rendering performance improvements
- Languages: Disable CSS property value completions, TS improved inference and const assertions
- Extension Authoring: Finalized smart selection API, install extension command
- Engineering: Official Linux snap package, faster OSS builds with NPM package caching


Visual Studio Code 1.32.3 (64-bit)

Fixed:
- Slow startup opening a large workspace over the network candidate file-explorer freeze-slow-crash important verified
- Fix #70045 by reverting some of #67269


Visual Studio Code 1.32.2 (64-bit)
- Preview and apply color themes: Install and apply new theme extensions without reloading
- Keyboard shortcuts editor improvements: Modify keybinding 'when' conditions in the editor
- Problems panel hover commands: Apply Quick Fixes or open a Peek window directly from hovers
- Preferred Code Actions: Preferred (mostly likely) Code Actions support auto fixing common issues
- Debug Console customization: Modify font size, font family, and line height of the Debug Console
- Better IntelliSense for ARIA attributes: More detailed descriptions for HTML accessibility attributes
- Vue.js interpolations IntelliSense: The Vetur extension now supports smart completions in Vue.js interpolations
- New "Bundling Extensions" topic: Use webpack to improve your extension's load time


Visual Studio Code 1.32.1 (64-bit)
- Preview and apply color themes: Install and apply new theme extensions without reloading
- Keyboard shortcuts editor improvements: Modify keybinding 'when' conditions in the editor
- Problems panel hover commands: Apply Quick Fixes or open a Peek window directly from hovers
- Preferred Code Actions: Preferred (mostly likely) Code Actions support auto fixing common issues
- Debug Console customization: Modify font size, font family, and line height of the Debug Console
- Better IntelliSense for ARIA attributes: More detailed descriptions for HTML accessibility attributes
- Vue.js interpolations IntelliSense: The Vetur extension now supports smart completions in Vue.js interpolations
- New "Bundling Extensions" topic: Use webpack to improve your extension's load time

Visual Studio Code 1.31.1 (64-bit)
- No reload on extension install: No interruptions when you install new extensions
- Tree UI improvements: Improved Explorer navigation and filtering, horizontal scrolling
- Main menu updates: Redesigned Go actions menu, Edit menu Cut command
- Multiline Problems output: See full multiline issue details in the Problems panel
- Find All References history: Quickly rerun previous reference searches
- Semantic selection for HTML, CSS, and JSON: Expand/shrink selection based on language semantics
- Integrated Terminal reflow support: Terminal text automatically reflows as panel width changes
- Command-based user input variables: Custom user input for task and debug configuration
- Updated Extension API documentation: Completely rewritten with extension guides


Visual Studio Code 1.31.0 (64-bit)
- No reload on extension install: No interruptions when you install new extensions
- Tree UI improvements: Improved Explorer navigation and filtering, horizontal scrolling
- Main menu updates: Redesigned Go actions menu, Edit menu Cut command
- Multiline Problems output: See full multiline issue details in the Problems panel
- Find All References history: Quickly rerun previous reference searches
- Semantic selection for HTML, CSS, and JSON: Expand/shrink selection based on language semantics
- Integrated Terminal reflow support: Terminal text automatically reflows as panel width changes
- Command-based user input variables: Custom user input for task and debug configuration
- Updated Extension API documentation: Completely rewritten with extension guides


Visual Studio Code 1.30.2 (64-bit)
- Change log not available for this version


Visual Studio Code 1.30.1 (64-bit)
Fixes:
- Search view breaks after starting a search while the previous search is still running
- Can't search CRLF files with non-regex multiline search
- Fix search CRLF files with non-regex multiline search
- HTML editor not working fully bug candidate html
- Peek editor tree color tokens are broken bug candidate editor-symbols regression tree
- Can't trigger "Load more Stack Frames" with keyboard
- treeResourceNavigator: fire onSelection also for keyboard events
- "Start Debugging" asks to choose environment when triggered from main menu


Visual Studio Code 1.30.0 (64-bit)
- Multiline search improvements: Easily create multiline search patterns without using regex
- Custom title bar on Linux: The custom title and menu bar is now the default on Linux
- References view: Find All References view includes history of recent searches
- Snippet comment variables: Snippet variables insert correct comment per language
- JS/TS callback display: Now you can see the context of anonymous callbacks
- JSDoc Markdown highlighting: Including syntax highlighting for Markdown code blocks in JSDoc
- Simplified debug configuration: Better defaults and Quick Pick UI for initial launch configuration
- Run tasks on folder open: Configure tasks to run when you first open a project folder
- Choose extension version: Install earlier versions of Marketplace extensions
- Workbench: Menu scrolling and improved overflow handling, one click to open settings.json
- Languages: JS/TS renames now handle destructuring, add missing 'new' Quick Fix
- Debugging: Delete debug consoles, debug directly from the VS Code Process Explorer
- Tasks: Clear task terminal, user input for task variables, rerun last task command
- Extension Authoring: Go to Declaration support, new Signature Help context


Visual Studio Code 1.29.1 (64-bit)
- Change log not available for this version


Visual Studio Code 1.29.0 (64-bit)
- Multiline search: Search across files with regex multiline expressions
- File icons in IntelliSense: Quickly distinguish file types in IntelliSense
- Better macOS support: Full screen mode control and Mojave Dark Mode support
- Collapsible stack frames: Collapse uninteresting stack frames to clearly see your code
- Improved Loaded Scripts view: Displays related resources such as original source files
- Updated extension samples: Uniform style and structure, README, and API usage
- CI recipe for extensions: Azure Pipelines build recipe for extensions
- Preview: List All References: List All References view shows reference search results
- If you'd like to read these release notes online, go to Updates on code.visualstudio.com
- You can also check out this 1.29 release highlights video from Cloud Developer Advocate Brian Clark


Visual Studio Code 1.28.2 (64-bit)
Fixed issues:
- September 2018 Recovery 2 Endgame
- Keep spawning powershell.exe and conhost.exe
- VSCode frequently crashes when ctrl+P searching after 1.28
- debug: on restart, make sure to first disconnect and only then run the prelaunch tasks
- “Remove from recent opened” takes no effect
- Restarting the debug process fails
- Apply selection even when the items don't change
- Auto import not being placed correctly
- Code completion for import suggestion stopped working
- Intellisense - Import suggestions show up but are not inserted/loaded


Visual Studio Code 1.28.1 (64-bit)
Release highlights:
- VS Code file icons reflect file type in your OS explorer
- Tune your snippet collection per workspace
- Use Tab to easily cycle through IntelliSense suggestions
- New command to go to the location of your last edit
- Save a file without changing the existing formatting
- Better delete conflict handling, new rebase on sync option
- Rename a JS/TS file through its import path
- Quickly update a function to use async and await
- Collapse code blocks, multi-line lists, and embedded HTML
- We decided to revisit the behavior of our commands for toggling panels (Terminal, Output, Problems, Debug Console). You can follow issue 19400 for the background on the change

The old behavior was:
- Panel shows if not visible
- Panel hides if visible

The new behavior is:
- Panel shows if not visible
- Panel hides if having keyboard focus
- Panel gets focused when visible but not focused


Visual Studio Code 1.28.0 (64-bit)
Fixes:
- After formatting you need to scroll left
- Must tab through deleted tab stops in snippets
- Debug toolbar buttons disabled
- "Clear Recently Opened" should also clear editor quick pick history
- Reveal untitled file when saving
- Preserve quick open input on Escape
- UriDisplayService is missing remote share path name
- Mechanism to abort the debug launch without showing launch.json
- Debug Hover Widget - Enable the widget resizing for long items whose overflow is hidden
- Conditional breakpoint prompt should offer to enable breakpoints if breakpoint is already disabled
- Extensions: allow to right click to bring up gear menu
- Use --force arg to prevent prompts while installing extensions from CLI


Visual Studio Code 1.27.2 (64-bit)
Fixed:
- August Recovery Endgame
- Regex search and group replace
- TreeItem.iconPath with non-file Uri can be encoded incorrectly
- Breadcrumb selection is broken
- removeFromRecentlyOpened Command Broken
- [html] jquery completions no longer work
- Cannot click relative paths in terminal
- August Recovery Endgame
- VS Code doesn't work after update
- Incorrect new settings (UI) behavior after nothing was found


Visual Studio Code 1.27.1 (64-bit)
- Change log not available for this version


Visual Studio Code 1.27 (64-bit)
Highlights:
- New Settings editor UI to discover, search, and modify VS Code settings
- Fully themable title and menu bars on Windows and Linux
- Symbols highlighted when navigating with breadcrumbs
- Combined menu for creating terminals and managing tasks
- Share the same keybindings.json file across different OSs
- Import path suggestions while you type in CSS, SCSS, and Less
- Support for 'if', 'then', and 'else' schema keywords
- Loaded Scripts Explorer now available for debug extensions


Visual Studio Code 1.26.1 (64-bit)
- Addresses these issues
- Extension host terminated unexpectedly after 1.26.0 update
- Problem entries loops
- Problem Tab is all corrupted with Typescript Problems
- RG 700% CPU usage
- Opened files are not searched until file tab is clicked
- Built-in git extension disabled
- VS Code Hangs When Opening Specific PowerShell File
- VSCode hangs when opening python file
- File paths in Open Recent Menu starts with / and lower case drive letter
- Editor layout is called on every config change


Visual Studio Code 1.26.0 (64-bit)
- Change log not available for this version


Visual Studio Code 1.25.1 (64-bit)
Fixed issues:
- June Recovery Endgame
- Recommended Extensions shows already installed extensions
- executeTask Cannot read property _key of undefined
- Allow task without task definitions. Treat all properties as mandantory
- Error while invoking command `Developer: Reinstall Extension`
- Unverified breakpoint error with build 1.25
- Portable Mode creates cache files in %APPDATA%


Visual Studio Code 1.25.0 (64-bit)
- Change log not available for this version


Visual Studio Code 1.24.1 (64-bit)
- Change log not available for this version


Visual Studio Code 1.24.0 (64-bit)
Some of the key highlights include:
- Unused variable detection - Unused variables are greyed-out in your JavaScript/TypeScript files
- Move to new file refactoring - Easily pull classes and functions into their own files
- Update imports on move/rename - Automatically update import paths in JavaScript/TypeScript
- Duplicate workspace in new window - Great for expanding over multi-mon setups
- IntelliSense for predefined variables - Variable suggestions in debug and task configuration files
- Preview: Outline view - Symbol tree outline and navigation for your projects
- Preview: Settings Editor - New GUI to discover and modify VS Code settings
- Preview: Debug toolbar location - Float, dock or hide the debug toolbar
- Preview: Grid editor layout - Custom vertical/horizontal layout, coming soon to Insiders
- Working with Docker and MongoDB - Learn about Docker and MongoDB integration in VS Code

Here are some further updates:
- Editor - Zoom font size independent of your workbench, syntax highlighting for deleted lines
- Integrated Terminal - Smart fallback to DOM renderer, italic and line spacing support
- Debugging - Switch to debug view on break, Go to Next/Previous Breakpoint
- Languages - JavaScript/TypeScript getter/setter refactoring, SCSS @-keyword completions
- Extension Authoring - Expanded custom views API, Task API to stable, new theme colors


Visual Studio Code 1.23.1 (64-bit)
- April Recovery Endgame endgame-plan
- Extension update events are not being reported using telemetry bug extensions verified
- instanceof doesn't work for FileSystemError api bug candidate remote verified
- Enable cascade to overwrite language features api bug debt verified
- Add undefined check to Quick Input command code path bug candidate verified
- Clear Terminal stops working after upgrading to v1.23.0 bug candidate integrated-terminal verified
- Windows key omitted from menu shortcut hint bug candidate verified


Visual Studio Code 1.23.0 (64-bit)
- Highlighted indent guides: Helps visualize source code indenting
- Run Code Actions on save: Run actions like Organize Imports when you save
- NPM script explorer: Quickly find, run, and debug NPM scripts in your project
- Problems view filtering: Choose which files will display errors and warnings
- Middle mouse button column selection: Middle mouse button with drag for fast column selection
- CSS region folding: Create regions in your CSS/SCSS/Less code for helpful code folding
- Improved CSS new property support: Smart suggestions for CSS experimental properties
- Markdown header search: Search for Markdown headers across your entire workspace
- Custom Activity Bar views: Extension authors can create their own Activity Bar items
- New deploy website tutorial: Learn how to deploy a static website to Azure Storage
- Editor: Better Unicode file support, more stable editor positioning
- Workbench: Copy search results, better Git clone workflow, VS Code process explorer
- Debugging: Logpoint expressions support smart completions and displaying structured objects
- Languages: JavaScript/TypeScript Organize Imports action, persistent Markdown previews
- Extension Authoring: New webview and FileSystem Provider APIs, 'Source' file level actions


Visual Studio Code 1.22.2 (64-bit)
- Syntax aware code folding: Adds improved folding for CSS, HTML, JSON, and Markdown files
- Cross file error, warning and reference navigation: Move quickly around your workspace
- New Hint suggestions: Makes it easy to spot suggested fixes or refactorings in the editor
- Convert to ES6 refactoring: New Code Actions to convert to ES6 classes and modules
- Auto attach to process: Automatically attach the debugger to running Node.js processes
- Logpoints: Inject logging without changing source code or restarting your debug session
- Better large file support: Faster syntax highlighting and easily increase memory for very large files
- Multi-line links in the terminal: Paths and URLs can span lines in the Integrated Terminal
- Emmet wrap preview: Live preview for Emmet's wrap with abbreviation functionality
- Improved updates on Windows: Automatically updates in the background for less downtime
- Preview: Organize JS/TS imports: Remove unused and sort remaining imports


Visual Studio Code 1.22.1 (64-bit)
- Change log not available for this version


Visual Studio Code 1.21.1 (64-bit)
The update addresses these issues:
- [Language Pack] tr is not supported to load "Turkish Language Pack"
- Dir

更新時間：2021-02-02
更新細節：

What's new in this version:

New:
- Added support for downloading audio in the original format
- Added subtitles selection to YouTube playlist/channel/bulk search
On the video trimmer screen, you can now switch between using the timestamp slider or - entering the timestamps manually

Added 3 new settings:
- Use numbered file names for YouTube chapters
- Bypass HTTPS certificate verification (advanced)
- Establish download connections using IPv6 (advanced)

Fixed:
- Fixed Bitchute download issues when One-Click mode is enabled
Retrying a download with error will now continue from the point that it was stopped (to save - bandwidth) rather than starting from the beginning

更新時間：2021-01-24
更新細節：

What's new in this version:

Updated:
- Less to 4.1.0
- Autoprefixer to 10.2.3
- Dart Sass to 1.32.5