fix: update dependencies and improve session management

[GordonSmith]

• Updated various dependencies in package.json primarily to fix the btoa polyfill issue with unicode chars
• Refactored session management in session.ts:
  • Removed credential migration on initialization (replaced with migrate on use).
  • Enhanced session switching logic to handle credentials more effectively.
  • Improved configuration updates to avoid unnecessary triggers.

[Copilot]

Pull request overview

This pull request updates dependencies (primarily to fix btoa polyfill unicode character issues) and refactors session management to migrate credentials on-demand rather than during initialization. The key changes improve configuration update efficiency and credential handling workflow.

• Updated @hpcc-js packages and related dependencies for unicode character handling fixes
• Refactored credential migration from initialization-time to on-demand (during session switch)
• Optimized configuration updates to prevent unnecessary event triggers

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
package.json	Minor version bumps for @hpcc-js packages (3.4.1→3.4.3, 3.5.1→3.5.3, 3.11.1→3.12.1, etc.), esbuild (0.27.0→0.27.1), vitest (4.0.10→4.0.15), and other dev dependencies
package-lock.json	Corresponding lockfile updates for dependency version changes
src/util/credentialManager.ts	Refactored Credentials.attach() caching logic, renamed migrateExistingCredentials to migrateLaunchConfigIfNeeded (now public), added removePasswordFromLaunchConfig helper
src/hpccplatform/session.ts	Removed automatic migration on initialize(), made switchTo async with on-demand migration, added conditional configuration updates, enhanced status bar refresh with credential checks
ecl-sample/.vscode/launch.json	Added test launch configurations with credential fields for testing unicode password support

[Copilot]

Pull request overview

Copilot reviewed 4 out of 5 changed files in this pull request and generated 8 comments.

Comments suppressed due to low confidence (1)

src/util/credentialManager.ts:57

• Potential issue with cache invalidation: When retrieving a password from secrets storage, the code directly modifies the cached Credentials object's _password field. However, if the password retrieval fails (caught in the catch block), the cached object will remain with an empty password. This could lead to stale cache entries.

Recommendation: Consider removing the cached entry if password retrieval fails, or add a flag to indicate the retrieval status:

try {
    const password = await context.secrets.get(storageKey);
    credentials._password = password ?? "";
} catch (e) {
    logger.error(`Failed to get password for ${user}@${baseUrl}: ${e}`);
    credentialManagerCache.delete(storageKey); // Remove stale cache entry
}

        try {
            const password = await context.secrets.get(storageKey);
            credentials._password = password;
        } catch (e) {
            logger.error(`Failed to get password for ${user}@${baseUrl}: ${e}`);
        }

[github-actions]

🎉 This change has been included in ecl-v2.33.2 🎉

The release is available on:

• GitHub releases: ecl: v2.33.2

Your release-please bot 🚀🙏