- BREAKING: dotnet 8
- potentially BREAKING: replace Nett by Tomlyn
- add: allow defining auxiliary tasks that can be run from the client
- fix: improve logging scopes and readability
- add: enable setting env vars in dotnet apps
- add: enable setting build configuration (Debug/Release) in dotnet apps
- fix: correctly read chunked messages on the client side
- BREAKING feat: use toml for configuring the ring itself
- BREAKING feat: make Kustomize runnables run directly in the OS ring runs in
- feat: process runnable - ability to run arbitrary processes
- feat: workspace flavours
- feat: allow overriding runnable
id
so it's now possible to run many instances of the same runnable - feat: log streaming
- fix: make behaviour of
workingDir
runnable configuration more intuitive
- feat: simplified import syntax (#38)
- fix: drain pub-sub before terminate (ensure all messages reach the clients) (#29)
- fix: configuration sources priority (environment vars should always take precedence) (#39)
- fix: could not use Urls override in aspnetcore runnable on Windows when running as exe (#39)
- chore: more reliable integration tests
- chore: use file-scoped namespaces
- fix: internal improvements around websockets
- fix: set VerisonPrefix in CI so the right version shows up in CLI
- feat: enable detection of a default workspace file in cwd (#20)
- fix: enable ring to run as a local tool
- Migrate to .NET 6
- Clone the default branch rather than hard-coded "master".
- Make core Ring cross-platform
- Optimisations
- Kustomize runnable: replace kubectl calls for direct API access
- IISExpress runnable: de-parallelise health checks
- Only add Uri detail if there are URLs
- Kustomize runnable: expose pod details
- RingVsix: added runnable context menu
- Use DetailsKeys
- Support for friendly name
- Fixed VSToolsPath
- Bump Vsix version
- KustomizeRunnable: improve init/start indication and other improvements
- git-supporting runnables: use shallow single-branch (master) clones
- kustomize runnables: enable built manifests caching
- Awaiting runnables to terminate on server shutdown
- Deleting corrupted git repos no longer fails with access denied errors
- Kustomize runnable health check correctly reacts on pods deletion/recreation
- Support for Kustomize apps
- Ring clone command
- Added support for user configuration
- no changes vs 2.3.4-pre. Releasing as the stable release before staring work on new features.
- bug fixes
- bug fixes
- Enabled cloning aspnetcore runnables source code from git.
- Fixed CsProj-based runnables trying to read from paths relative to the root working dir rather than the absolute ones. It was happening only if imported workspaces were in different folders.
- Added IISXCore runnable (ASP.NET Core on IIS Express)
- Upgraded to .NET Core 3.1
- Fixed iisexpress temp dir creation if does not exist
- Fixed pulling re-tagged Docker images (like latest)
Upgraded to NET Core 3
- IISExpress Runnable: enable retrieval of custom binding information from csproj files
Ring uses /Project/ProjectExtensions/VisualStudio/FlavorProperties/WebProjectProperties
to determine how to run a particular project.
So far it used DevelopmentServerPort
and assume localhost
. From now on it will use the URL specified at IISUrl
instead.
- Bugfixes
- Logging improvements.
- Fixed System.ArgumentOutOfRangeException if runnable is dead.
- Fixed swallowing exceptions if one of the base tasks fails.
- Fixed Microsoft.AspNetCore.WebSockets reference.
- Added support for docker-compose files
- Fixed a bug on capturing output of exited processes