Skip to content

Prepare 3.0.3 release #1582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Prepare 3.0.3 release #1582

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4616ce8
Prepare 3.0.3 release
isc-bsaviano Jun 10, 2025
68ce09c
Update CHANGELOG.md
isc-bsaviano Jun 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,27 @@
# Change Log

## [3.0.3] 16-Jun-2025
- Enhancements
- Cache the contents of files fetched during a debug session (#1579)
- Fixes
- Fix `objectscript.autoAdjustName` behavior with `Save As...` (#1562)
- Fix detection of duplicate file change events (#1564)
- Attempt to use existing line endings when replacing a file's contents post-compile (#1567)
- Exempt files created due to server export from `objectscript.autoAdjustName` behavior (#1571)
- Prevent rare case where a file may be compiled twice due to concurrency issues (#1571)
- Improve code that exempts post-save compile from the batching behavior (#1571)
- Update the VS Code editor UI if a server-side document was changed during save (#1573)
- Don't show `Show Plan` CodeLenses inside string literals (#1574)
- Fix timeout of connection requests on activation (#1577)
- Fix the automatic termination of REST and unit test debug sessions (#1579)
- Prevent VS Code from showing a `Create File` button for files that are deployed when debugging (#1579)
- Don't attempt to set a breakpoint that's from a file in a different workspace folder (#1579)
- Fix debugging files in a client-side virtual workspace folder (#1579)
- Explicitly report failure to set a breakpoint (#1579)
- Use the document index to get determine the name of a document in a local file when debugging (#1579)
- Handle errors when fetching server-side source control menu options fails (#1580)
- Fix saving and re-opening of server-side documents on VS Code 1.101.0 (#1584)

## [3.0.2] 20-May-2025
- Enhancements
- Allow `objectscript.multilineMethodArgs` to be set per workspace folder (#1534)
Expand Down
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,8 +55,8 @@ To unlock these features (optional):

1. Download and install a beta version from GitHub. This is necessary because Marketplace does not allow publication of extensions that use proposed APIs.
- Go to https://github.com/intersystems-community/vscode-objectscript/releases
- Locate the beta immediately above the release you installed from Marketplace. For instance, if you installed `3.0.2`, look for `3.0.3-beta.1`. This will be functionally identical to the Marketplace version apart from being able to use proposed APIs.
- Download the VSIX file (for example `vscode-objectscript-3.0.3-beta.1.vsix`) and install it. One way to install a VSIX is to drag it from your download folder and drop it onto the list of extensions in the Extensions view of VS Code.
- Locate the beta immediately above the release you installed from Marketplace. For instance, if you installed `3.0.3`, look for `3.0.4-beta.1`. This will be functionally identical to the Marketplace version apart from being able to use proposed APIs.
- Download the VSIX file (for example `vscode-objectscript-3.0.4-beta.1.vsix`) and install it. One way to install a VSIX is to drag it from your download folder and drop it onto the list of extensions in the Extensions view of VS Code.

2. From [Command Palette](https://code.visualstudio.com/docs/getstarted/tips-and-tricks#_command-palette) choose `Preferences: Configure Runtime Arguments`.
3. In the argv.json file that opens, add this line (required for both Stable and Insiders versions of VS Code):
Expand Down