#breakingchange — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #breakingchange, aggregated by home.social.
-
Check out .NET 10's amazing features now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Check out .NET 10's amazing features now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Check out .NET 10's amazing features now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Check out .NET 10's amazing features now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Check out .NET 10's amazing features now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency
https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe… -
Here are some examples of breaking changes in REST APIs you should avoid.
Read more 👉 https://lttr.ai/AqCXX
-
Here are some examples of breaking changes in REST APIs you should avoid.
Read more 👉 https://lttr.ai/AqCXX
-
Here are some examples of breaking changes in REST APIs you should avoid.
Read more 👉 https://lttr.ai/AqCXX
-
Here are some examples of breaking changes in REST APIs you should avoid.
Read more 👉 https://lttr.ai/AqCXX
-
REST API Basics: Breaking Changes
▸ https://lttr.ai/ApKSg -
REST API Basics: Breaking Changes
▸ https://lttr.ai/ApKSg -
REST API Basics: Breaking Changes
▸ https://lttr.ai/ApKSg -
When designing REST APIs, one of the biggest challenges is avoiding breaking changes, modifications that force existing clients to update their code.
Read more 👉 https://lttr.ai/AoZ4X
-
When designing REST APIs, one of the biggest challenges is avoiding breaking changes, modifications that force existing clients to update their code.
Read more 👉 https://lttr.ai/AoZ4X
-
When designing REST APIs, one of the biggest challenges is avoiding breaking changes, modifications that force existing clients to update their code.
Read more 👉 https://lttr.ai/AoZ4X
-
Explore awesome new features in .NET 10—out now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Explore awesome new features in .NET 10—out now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Explore awesome new features in .NET 10—out now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Explore awesome new features in .NET 10—out now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Explore awesome new features in .NET 10—out now! https://www.funkysi1701.com/posts/2025/blazor-and-dotnet10/ #Blazor #.NET10 #WebAssembly #Wasm #HttpClient #breakingchange #DotNet #VisualStudio #release #streamingresponse #C-Sharp
-
Quick headsup, #paperlessngx braucht wohl ab 2.18 mindestens Postgres 14 … und wer hat’s wieder verpennt ;) #breakingchange #selfhosting.
-
Quick headsup, #paperlessngx braucht wohl ab 2.18 mindestens Postgres 14 … und wer hat’s wieder verpennt ;) #breakingchange #selfhosting.
-
Quick headsup, #paperlessngx braucht wohl ab 2.18 mindestens Postgres 14 … und wer hat’s wieder verpennt ;) #breakingchange #selfhosting.
-
Quick headsup, #paperlessngx braucht wohl ab 2.18 mindestens Postgres 14 … und wer hat’s wieder verpennt ;) #breakingchange #selfhosting.
-
Zig breaking change – initial Writergate
https://github.com/ziglang/zig/pull/24329
#HackerNews #Zig #Writergate #breakingchange #programming #language #GitHub #open #source
-
Zig breaking change – initial Writergate
https://github.com/ziglang/zig/pull/24329
#HackerNews #Zig #Writergate #breakingchange #programming #language #GitHub #open #source
-
Zig breaking change – initial Writergate
https://github.com/ziglang/zig/pull/24329
#HackerNews #Zig #Writergate #breakingchange #programming #language #GitHub #open #source
-
Zig breaking change – initial Writergate
https://github.com/ziglang/zig/pull/24329
#HackerNews #Zig #Writergate #breakingchange #programming #language #GitHub #open #source
-
Zig breaking change – initial Writergate
https://github.com/ziglang/zig/pull/24329
#HackerNews #Zig #Writergate #breakingchange #programming #language #GitHub #open #source
-
BinaryFormatter removed from .NET 9 by Immo Landwerth.
#dotnet #csharp #breakingchange #security #dotnet9
https://devblogs.microsoft.com/dotnet/binaryformatter-removed-from-dotnet-9/ -
BinaryFormatter removed from .NET 9 by Immo Landwerth.
#dotnet #csharp #breakingchange #security #dotnet9
https://devblogs.microsoft.com/dotnet/binaryformatter-removed-from-dotnet-9/ -
BinaryFormatter removed from .NET 9 by Immo Landwerth.
#dotnet #csharp #breakingchange #security #dotnet9
https://devblogs.microsoft.com/dotnet/binaryformatter-removed-from-dotnet-9/ -
BinaryFormatter removed from .NET 9 by Immo Landwerth.
#dotnet #csharp #breakingchange #security #dotnet9
https://devblogs.microsoft.com/dotnet/binaryformatter-removed-from-dotnet-9/ -
BinaryFormatter removed from .NET 9 by Immo Landwerth.
#dotnet #csharp #breakingchange #security #dotnet9
https://devblogs.microsoft.com/dotnet/binaryformatter-removed-from-dotnet-9/ -
Well, given that I am about to perpetrate a #breakingchange I figure I should put some sort of versioning on #allthethings so that we can perform its #rollout with as few surprises as possible. I don’t know what order of #environments we will do (there may be some #nonproduction environments both before and after #production) but at least we will be able to track what knobs we turned and what levers we threw to get there. (Or rescue ourselves!)
If only it weren’t such a giant #chore.
-
Heads up anyone playing with Kitten at the moment (yes, both of you):
I’m in the process of upgrading Kitten’s version of JSDB from 4 to 5.
*This is a breaking change.*
This will affect you if you’re persisting custom objects (instances of your custom model classes) in your databases.
Please see the details in this JSDB announcement post and the linked-to details page to prepare:
https://mastodon.ar.al/@aral/112361559531645603
(I should have the update out this afternoon.)
-
Heads up anyone playing with Kitten at the moment (yes, both of you):
I’m in the process of upgrading Kitten’s version of JSDB from 4 to 5.
*This is a breaking change.*
This will affect you if you’re persisting custom objects (instances of your custom model classes) in your databases.
Please see the details in this JSDB announcement post and the linked-to details page to prepare:
https://mastodon.ar.al/@aral/112361559531645603
(I should have the update out this afternoon.)
-
Heads up anyone playing with Kitten at the moment (yes, both of you):
I’m in the process of upgrading Kitten’s version of JSDB from 4 to 5.
*This is a breaking change.*
This will affect you if you’re persisting custom objects (instances of your custom model classes) in your databases.
Please see the details in this JSDB announcement post and the linked-to details page to prepare:
https://mastodon.ar.al/@aral/112361559531645603
(I should have the update out this afternoon.)
-
Heads up anyone playing with Kitten at the moment (yes, both of you):
I’m in the process of upgrading Kitten’s version of JSDB from 4 to 5.
*This is a breaking change.*
This will affect you if you’re persisting custom objects (instances of your custom model classes) in your databases.
Please see the details in this JSDB announcement post and the linked-to details page to prepare:
https://mastodon.ar.al/@aral/112361559531645603
(I should have the update out this afternoon.)
-
Heads up anyone playing with Kitten at the moment (yes, both of you):
I’m in the process of upgrading Kitten’s version of JSDB from 4 to 5.
*This is a breaking change.*
This will affect you if you’re persisting custom objects (instances of your custom model classes) in your databases.
Please see the details in this JSDB announcement post and the linked-to details page to prepare:
https://mastodon.ar.al/@aral/112361559531645603
(I should have the update out this afternoon.)
-
Kitten breaking change: Route handlers, etc., now take parameter objects
Just pushed the API updates I’d posted about earlier to main and to the latest Kitten release.
This change affects:
- Route handlers (all types of routes)
- `onConnect()` handlers
- The default export on main.script.js filesI’ve updated all the examples, documentation, etc., on Kitten to use the new API but if you see anything I’ve missed, please let me know.
-
Kitten breaking change: Route handlers, etc., now take parameter objects
Just pushed the API updates I’d posted about earlier to main and to the latest Kitten release.
This change affects:
- Route handlers (all types of routes)
- `onConnect()` handlers
- The default export on main.script.js filesI’ve updated all the examples, documentation, etc., on Kitten to use the new API but if you see anything I’ve missed, please let me know.
-
Kitten breaking change: Route handlers, etc., now take parameter objects
Just pushed the API updates I’d posted about earlier to main and to the latest Kitten release.
This change affects:
- Route handlers (all types of routes)
- `onConnect()` handlers
- The default export on main.script.js filesI’ve updated all the examples, documentation, etc., on Kitten to use the new API but if you see anything I’ve missed, please let me know.
-
Kitten breaking change: Route handlers, etc., now take parameter objects
Just pushed the API updates I’d posted about earlier to main and to the latest Kitten release.
This change affects:
- Route handlers (all types of routes)
- `onConnect()` handlers
- The default export on main.script.js filesI’ve updated all the examples, documentation, etc., on Kitten to use the new API but if you see anything I’ve missed, please let me know.
-
Kitten breaking change: Route handlers, etc., now take parameter objects
Just pushed the API updates I’d posted about earlier to main and to the latest Kitten release.
This change affects:
- Route handlers (all types of routes)
- `onConnect()` handlers
- The default export on main.script.js filesI’ve updated all the examples, documentation, etc., on Kitten to use the new API but if you see anything I’ve missed, please let me know.