hunk.code_window: ## Using Release Channels for Environment Variable Configuration
   Enironment variables don't exist explicitly, but you can utilize release channels to make that happen!
   Say you have a workflow of releasing builds like this:
   - `exp publish --release-channel prod-v1`
   - `exp publish --release-channel prod-v2`
  
hunk.labels: keep keep replace keep keep keep keep keep
hunk.after_edit: Environment variables don't exist explicitly, but you can utilize release channels to make that happen!
  
hunk.file_path: docs/versions/unversioned/guides/release-channels.md
hunk.type: replace
file: /**
   * Copyright (c) 2015-present, Facebook, Inc.
   *
   * This source code is licensed under the MIT license found in the
   * LICENSE file in the root directory of this source tree.
   */
  
  #import "ABI29_0_0RCTAnimatedNode.h"
  
  @interface ABI29_0_0RCTTransformAnimatedNode : ABI29_0_0RCTAnimatedNode
  
  - (NSDictionary<NSString *, NSObject *> *)propsDictionary;
  
  @end
  