updates

Author: isaacsas

HISTORY.md

@@ -1,14 +1,19 @@
 # Breaking updates and feature summaries across releases
 
 ## Catalyst unreleased (master branch)
+- Scoped species/variables/parameters are now treated similar to the latest MTK releases (≥ 9.49).
 - Array symbolics support is more consistent with ModelingToolkit v9. Parameter arrays are no longer scalarized by Catalyst, while species and variables arrays still are (as in ModelingToolkit). As such, parameter arrays should now be specified as arrays in value mappings, i.e.
   ```julia
   @parameters k[1:4]
   pmap = [k => rand(4)]
   ```
-  While one can still manually scalarize a parameter array, it is recommended *not* to do this as it has signifcant performance costs with ModelingToolkit v9.
+  While one can still manually scalarize a parameter array, it is recommended
+  *not* to do this as it has signifcant performance costs with ModelingToolkit
+  v9. Note, scalarized parameter arrays passed to the two-argument constructor
+  `ReactionSystem` may become unscalarized.
 - The structural identifiability extension is currently disabled due to issues StructuralIdentifiability has with Julia 1.10.5 and 1.11.
 - A tutorial on making interactive plot displays using Makie has been added.
+- The BifurcationKit extension has been updated to v.4.
 
 ## Catalyst 14.4.1
 - Support for user-defined functions on the RHS when providing coupled equations 

docs/src/devdocs/dev_guide.md

@@ -6,10 +6,11 @@ continuing stability of releases. Before making a release one should
 
 1. Create a new release branch, i.e. "release-15.0.0"
 2. On this branch, cap major dependencies to their latest version that works and
-   passes test.
+   for which tests pass.
    - Caps need to be included in both Project.toml and docs/Project.toml.
    - Do not cap the master branch as this can prevent upstream libraries from
-     properly testing against Catalyst.
+     properly testing against Catalyst, and hide breaking changes that impact
+     Catalyst.
 3. Check docs build with the capped dependencies. Visually verify via checking
    the artifact in the doc build that the docs actually look ok (since sometimes
    issues can arise that do not lead to actual errors in the doc CI).