fix: use similar update method.

Author: l-monninger

aptos-move/aptos-release-builder/src/components/feature_flags.rs

@@ -185,9 +185,16 @@ pub fn generate_feature_upgrade_proposal(
             generate_features_blob(writer, &disabled);
             emitln!(writer, ";\n");
 
+            let update_method = if is_testnet {
+                "change_feature_flags"
+            } else {
+                "change_feature_flags_for_next_epoch"
+            };
+
             emitln!(
                 writer,
-                "features::change_feature_flags_for_next_epoch({}, enabled_blob, disabled_blob);",
+                "features::{}({}, enabled_blob, disabled_blob);",
+                update_method,
                 signer_arg
             );
             emitln!(writer, "aptos_governance::reconfigure({});", signer_arg);

aptos-move/framework/move-stdlib/sources/configs/features.move

@@ -636,9 +636,11 @@ module std::features {
     ///
     /// Genesis/tests should use `change_feature_flags_internal()` for feature vec initialization.
     ///
+    /// This can be used on testnet prior to successful DKG.
+    ///
     /// Governance proposals should use `change_feature_flags_for_next_epoch()` to enable/disable features.
-    public fun change_feature_flags(_framework: &signer, _enable: vector<u64>, _disable: vector<u64>) {
-        abort (error::invalid_state(EAPI_DISABLED))
+    public fun change_feature_flags(framework: &signer, enable: vector<u64>, disable: vector<u64>) {
+        change_feature_flags_internal(framework, enable, disable)
     }
 
     /// Update feature flags directly. Only used in genesis/tests.